MCP server for Codex
Cold email MCP server for Codex
Codex already works in your terminal and repo. Add Outreach2day and it runs your sending setup too: domains, mailboxes, warmup, campaigns and replies, with every payment approved by you on Stripe.
codex mcp add outreach2day --url https://public.outreach2day.com/mcp
codex mcp login outreach2dayCopies the commands to add the server and open sign-in
Setup guide
- Run the copied commands in your terminal
- Sign in with your Outreach2day account
- Run codex mcp list to check the connection
Use an install script
curl -fsSL https://outreach2day.com/install | sh -s -- --client codex$env:O2D_CLIENT="codex"; irm https://outreach2day.com/install.ps1 | iexAdds the server to Codex, after a backup of each config. Each client asks you to sign in to Outreach2day on first use. View the script
- Orders paid through Stripe after you approve them
- $2.50 per mailbox a month
Check warmup on all mailboxes and write a status table to docs/sending.md.
called outreach2day tools
40 mailboxes: 34 ready, 6 warming (ready in 3 to 5 days).
Wrote docs/sending.md with inbox rate per mailbox.
Lowest: sam@getacme.info at 71%. Pause the campaign it sends in?
- teams have used Outreach2day
- 3,600+
- emails sent a day
- 40M+
Among them
Can Codex run cold email through MCP?
Yes. codex mcp add with the server URL, then codex mcp login, gives Codex tools for domains, mailboxes, warmup, campaigns and replies; you pay each order on Stripe.
Cold email in Codex, step by step
- 1
Add the server
One codex mcp add command, or a block in ~/.codex/config.toml, then codex mcp login to sign in with Prepare orders turned on
- 2
Script the setup
Codex checks domains, quotes the order and gives you the Stripe link. You pay; Codex follows the order
- 3
Keep state in the repo
Codex writes warmup and campaign status into files you version, next to your copy and lead lists
- 4
Launch and report
After 14 days of warmup Codex launches the campaign and reports replies and per-mailbox numbers on request
Outreach2day in Codex: where to connect
- OAuth sign-in
Codex CLI
codex mcp add with --url, then codex mcp login
Codex docs: configuration reference
Setup details
Codex: files, sign-in and limits
What Codex's own documentation says about connecting a remote MCP server.
- Config file
- ~/.codex/config.toml. A project's .codex/config.toml loads only when the project is trusted. The Codex CLI, the IDE extension and the ChatGPT desktop app share this configuration. Codex docs: MCP
- Auth
- codex mcp login outreach2day signs in with OAuth and Codex keeps the token. Without a browser, bearer_token_env_var names the environment variable that holds your key; Codex sends it as a Bearer token and the key stays out of the file. http_headers and env_http_headers add other headers. Codex docs: configuration referenceAuth
# or by hand, in ~/.codex/config.toml[mcp_servers.outreach2day]url = "https://public.outreach2day.com/mcp" - Approvals
- default_tools_approval_mode per server: auto, prompt, writes or approve. enabled_tools and disabled_tools limit the list. Codex docs: configuration reference
- Timeouts
- startup_timeout_sec defaults to 10 seconds and tool_timeout_sec to 60. required = true makes Codex stop if the server does not start. Codex docs: configuration reference
- Transport
- Streamable HTTP for a url entry; stdio for local command entries. Codex docs: configuration reference
Works with Outreach2day
- Codex CLI, the IDE extension and the ChatGPT desktop app from one config.toml
- OAuth with codex mcp login, or a Bearer key from an environment variable
Does not work
- A key written into config.toml: bearer_token_env_var takes the variable's name
- A project .codex/config.toml in a folder you have not trusted
The tools Codex gets and the guardrails on orders are the same in every client: tool list, what the agent can and cannot do.
Prompts
Things to ask Codex
Plain language is enough. The agent picks the tools and asks before anything costs money.
- Check warmup on all mailboxes and write a status table to docs/sending.md.
- Quote 3 domains and 12 mailboxes for acme.com.
- Create a campaign from copy/sequence.md and leads/q4.csv, keep it as a draft.
- Run the preflight check on the Q4 campaign and fix what it flags in the copy.
- Pull yesterday's replies and append the interested ones to crm/leads.csv.
What Codex can do with the server, job by job
Each page lists the tools for the job, an example session, prompts per assistant and the limits.
- Outbound end to endDomains, mailboxes, warmup, campaign and replies from one assistant
- Domains and mailboxesCheck names, quote, pay on Stripe and track setup; or connect your own domains
- WarmupStart warmup and get inbox rate, spam rate and ready date per mailbox
- CampaignsDraft the sequence, import contacts, launch, read stats and replies
Setup
Connect Codex
Add https://public.outreach2day.com/mcp to Codex and sign in with your Outreach2day account when it asks. Then ask: "Check my Outreach2day account status". An API key is only for CI and headless setups.
Setup steps
Codex CLI
- Add the server with codex mcp add, or put the block in ~/.codex/config.toml
- Run codex mcp login outreach2day
- The first time the client connects, it opens an Outreach2day sign-in page in your browser. Sign in, turn on Prepare orders so the assistant can quote orders and create Stripe checkout links, and allow access
- Run codex mcp list to check it
codex mcp add outreach2day --url https://public.outreach2day.com/mcpcodex mcp login outreach2day # or by hand, in ~/.codex/config.toml[mcp_servers.outreach2day]url = "https://public.outreach2day.com/mcp"Or set up Codex CLI on this computer with one command
curl -fsSL https://outreach2day.com/install | sh -s -- --client codex$env:O2D_CLIENT="codex"; irm https://outreach2day.com/install.ps1 | iexSets up Codex CLI and adds the server by URL, after a backup of each config. Each client asks you to sign in to Outreach2day on first use. View the script
Book a call
Book a 30-minute call
Talk to the team that runs the MCP server. We check your setup for Codex and your first order.
- Free 30-minute call
- Size domains and mailboxes for your volume
- Walk through a quote and the Stripe checkout
- Check your Codex setup
See open times in your time zone and book on this page.
Or open the booking pageLoading available times…
Open the booking page insteadCustomers
Teams that send with Outreach2day
“That was the best infrastructure and value for money I saw.”
“…deliverability with your inboxes is better than our outlook/google inboxes…”
“We really would like to thank you for that report. We don’t know what we are doing with email and it is very reassuring to us to know we have a partner on top of the ball.”
Questions
Or talk to the teamHow does Codex authenticate to the Outreach2day MCP server?
With OAuth: codex mcp login outreach2day opens the sign-in page and Codex keeps the token. For CI, put an API key in $OUTREACH2DAY_API_KEY and set bearer_token_env_var = "OUTREACH2DAY_API_KEY"; the key never goes into config.toml.
Can Codex call write tools without asking?
Set default_tools_approval_mode to writes or approve and Codex asks before those calls. Launch also needs your confirmation on our side, and it is refused until the mailboxes have 14 days of warmup and the preflight check passes.
Do the Codex IDE extension and the ChatGPT desktop app need their own setup?
No. They read the same ~/.codex/config.toml as the CLI.
Other AI clients
The same server and the same tools in every client. Only the setup differs.
Guides for MCP and the API
- Cold Email API for Domains, Warmup and RepliesWhat the Outreach2day cold email API covers: keys, workspaces, domain checks and purchase, mailbox lists, warmup, replies and export to Instantly or Smartlead.
- MCP for Cold Email Infrastructure: Domains and MailboxesGive an AI agent your cold email infrastructure through MCP: check domains, connect your own, list mailboxes. Which actions to allow, which to keep manual.
- Email Warmup API: Start, Pause and MonitorHow to run mailbox warmup through the Outreach2day email warmup API: enable, pause and disable operations, idempotency keys, polling and warmup states.
Run cold email from Codex
Domains, mailboxes, warmup, campaigns and replies from Codex. You approve every order.