MCP server for Claude
Cold email MCP server for Claude
Ask Claude to buy 3 domains and 12 mailboxes, warm them up and launch your sequence. With Prepare orders turned on at sign-in, Claude quotes the order, you pay on Stripe, and Claude reports each step until replies come in.
https://public.outreach2day.com/mcp
Opens Claude with your server URL filled in. Sign in to Outreach2day to finish.
Setup guide
- Click Add, then Connect
- Sign in with your Outreach2day account
- Enable Outreach2day in your conversation
- Orders paid through Stripe after you approve them
- $2.50 per mailbox a month
Which mailboxes are still warming, and when is each one ready?
called outreach2day tools
12 mailboxes on 3 domains. 8 are ready, 4 are on day 11 of warmup.
The 4 on getacme.info are ready on Oct 2. Inbox rate so far: 93%.
The Q4 campaign can start with the 8 ready mailboxes. Attach them?
- teams have used Outreach2day
- 3,600+
- emails sent a day
- 40M+
Among them
Can Claude run cold email through MCP?
Yes. Add the server in Claude Code, or as a custom connector in claude.ai and Claude Desktop, and sign in to Outreach2day when Claude asks, with Prepare orders turned on. Claude checks domains, quotes mailboxes, runs warmup, launches campaigns and reads replies while you pay each order on Stripe.
Cold email in Claude, step by step
- 1
Plan the setup
Tell Claude your domain and daily volume; it checks free names, sizes domains and mailboxes and asks for a quote
- 2
Approve and pay
Claude shows the quote and waits for your yes; you pay on the Stripe page it links; card details stay with Stripe
- 3
Warm up
Claude follows the order through DNS and mailbox creation, starts warmup and reports each mailbox's inbox rate
- 4
Launch and read replies
After 14 days of warmup Claude attaches the mailboxes, runs the preflight check, launches, and summarizes replies when you ask
Outreach2day in Claude: where to connect
- OAuth sign-in
claude.ai, Claude Desktop and mobile
A custom connector: Customize, Connectors, Add custom connector, then sign in. Free plans get one custom connector
Claude docs: add a custom connector - OAuth sign-in
Claude Code
claude mcp add --transport http --scope user with the server URL, then sign in from /mcp
Claude Code docs: MCP
Setup details
Claude: files, sign-in and limits
What Claude's own documentation says about connecting a remote MCP server.
- Claude Code
- Add the server by URL, then sign in from /mcp (Authenticate) or with claude mcp login outreach2day. --scope user makes it available in every project; the default scope (local) keeps it to the folder you ran the command in, and project writes .mcp.json for the team. Claude Code docs: MCPClaude Code
claude mcp add --transport http --scope user outreach2day https://public.outreach2day.com/mcp - Key from the environment
- No browser? Add --header 'Authorization: Bearer ${OUTREACH2DAY_API_KEY}' in single quotes, so the variable is read when Claude Code connects and the key stays out of the config. In .mcp.json, header values expand environment variables the same way. Check the connection with /mcp or claude mcp list. Claude Code docs: MCP
- claude.ai, Desktop and mobile
- Customize, Connectors, Add custom connector, paste the server URL and sign in with your Outreach2day account (OAuth). The Free plan allows one custom connector. On Team and Enterprise an Owner adds it under Organization settings, Connectors; members then click Connect. Claude docs: add a custom connector
- API key in a connector
- Choose No sign-in and add an Authorization header under Request headers. The option is in beta for a limited set of organizations, and Claude sends the value exactly as typed, so include "Bearer ". Claude docs: connector authentication
- Claude Desktop config file
- ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows. The file runs local servers; add a remote server like Outreach2day as a custom connector instead. MCP docs: Claude Desktop config file
- Transport
- Streamable HTTP. Claude Code also speaks stdio and the older SSE transport; connectors use Streamable HTTP. Claude Code docs: MCP
Works with Outreach2day
- Claude Code with OAuth (/mcp) or an API key header
- claude.ai, Claude Desktop and mobile connectors with OAuth sign-in
Does not work
- Editing a connector's sign-in method: remove the connector and add it again
- Tool results over about 150,000 characters in claude.ai and Desktop, or tool calls longer than 240 seconds
- Server names with characters other than letters, digits, - and _ in Claude Code
The tools Claude 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 Claude
Plain language is enough. The agent picks the tools and asks before anything costs money.
- Set up cold email for acme.com: 3 domains, 12 mailboxes. Quote it and send me the payment link.
- Connect acme-mail.com, which I already own, and give me the DNS records to set.
- Draft a 4-step sequence for agency owners, check it for spam words, and keep it as a draft.
- Export the warm mailboxes on tryacme.com to our Smartlead workspace.
- Summarize replies from the last 24 hours and list the ones that ask for a call.
- Pause any campaign where a mailbox's bounce rate is above 3%.
What Claude 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 Claude
Add https://public.outreach2day.com/mcp to Claude 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
claude.ai, Claude Desktop and mobile
- In claude.ai or Claude Desktop, open Customize, Connectors, click + and choose Add custom connector
- Paste the server URL, https://public.outreach2day.com/mcp, and click Connect
- 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
- The connector then works in claude.ai, Claude Desktop and the mobile apps. Remote servers go in as connectors; claude_desktop_config.json is for local servers
Claude Code
- Add the server with the command below (user scope: every project)
- In Claude Code, run /mcp, pick outreach2day and choose Authenticate. Or run claude 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
- No browser (CI, a headless box)? Use an API key instead: put it in $OUTREACH2DAY_API_KEY and add --header 'Authorization: Bearer ${OUTREACH2DAY_API_KEY}' to the command (single quotes: Claude Code reads the variable when it connects)
claude mcp add --transport http --scope user outreach2day https://public.outreach2day.com/mcp# then, in Claude Code: /mcp, outreach2day, AuthenticateOr set up Claude Code on this computer with one command
curl -fsSL https://outreach2day.com/install | sh -s -- --client claude$env:O2D_CLIENT="claude"; irm https://outreach2day.com/install.ps1 | iexSets up Claude Code 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 Claude 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 Claude 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 teamWhich Claude apps can connect to the Outreach2day MCP server?
Claude Code (claude mcp add with the server URL), and claude.ai, Claude Desktop and the mobile apps as a custom connector. Each one signs in to Outreach2day with OAuth the first time it connects; no API key is needed.
Why is the server missing in another folder of Claude Code?
claude mcp add defaults to local scope: the server exists only in the project where you ran it. Add it again with --scope user to use it everywhere.
Does Claude need to run the whole setup in one chat?
No. Every call returns the current state and the next step, so you can come back days later and ask Claude where the order or the warmup stands.
Other AI clients
The same server and the same tools in every client. Only the setup differs.
Guides for MCP and the API
- Best MCP Servers for Cold Email and Outreach (2026), Ranked17 cold email and outreach MCP servers ranked by what an agent can do, how sends and purchases are confirmed, and hosting and auth. Sourced, re-checked Sep 29.
- Cold Email MCP Server: What It Is and How to Connect OneWhat a cold email MCP server does, the 23 tools of Outreach2day's hosted server, OAuth setup in Claude, Cursor and ChatGPT, and a session from quote to launch.
- 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.
Run cold email from Claude
Domains, mailboxes, warmup, campaigns and replies from Claude. You approve every order.