MCP for email warm-up

Email warm-up you start and check from your AI assistant

Your assistant starts warm-up on new mailboxes and answers the question that matters before a launch: which mailboxes are ready, and when the rest will be. Inbox rate, spam rate and ready date per mailbox.

https://public.outreach2day.com/mcp
Add to Claude

Opens Claude with your server URL filled in. Sign in to Outreach2day to finish.

Setup guide
  1. Click Add, then Connect
  2. Sign in with your Outreach2day account
  3. Enable Outreach2day in your conversation
Using Claude Code?
  • Orders paid through Stripe after you approve them
  • $2.50 per mailbox a month
Claude · Outreach2day MCP

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 warm-up.

The 4 on getacme.info are ready in 3 days. Inbox rate so far: 93%.

No mailbox shows a spam rate above 5%.

Is there an MCP server for email warm-up?

Yes. The Outreach2day MCP server has two warm-up tools: start_warmup turns warm-up on for mailboxes in your workspace, and get_warmup_status returns each mailbox's state, days warming, inbox rate, spam rate and ready date. A mailbox can join a campaign 14 days after warm-up starts.

Tools

What the agent can do

The tools the assistant calls for this job. Prepare orders is a switch on the sign-in page; Your yes means the tool runs only after you agree in the chat.

Warm-up

  • start_warmupStart warm-up on mailboxes; a retry the same day starts nothing twice
  • get_warmup_statusPer mailbox: warm-up state, days warming, ready flag and date, inbox rate and spam rate

Context

  • list_mailboxesMailbox address, sender name and status; no credentials
  • get_account_statusWhat the workspace has: domains and mailboxes by state, warm-up, open orders, campaigns, and the next step
  • attach_campaign_mailboxesAttach mailboxes whose warm-up started 14 or more days ago

Step by step

From new mailboxes to ready to send

What you ask, the tools the assistant calls, and what it answers, step by step.

  1. 1

    Find mailboxes that are not warming

    You: Which of my mailboxes have no warm-up yet?

    called get_warmup_status

    Agent: 4 mailboxes on getacme.info are not_started. The other 8 are warming, day 9.

  2. 2

    Start warm-up

    You: Start it on those 4.

    called start_warmup

    Agent: Warm-up requested for 4 of 4 mailboxes. They are ready to send in 14 days.

  3. 3

    Check progress

    You: How is warm-up going?

    called get_warmup_status

    Agent: 8 mailboxes on day 12, inbox rate 94%, spam rate 2%. The 4 new ones on day 3. First 8 ready in 2 days.

  4. 4

    Use the ready ones

    You: Attach the ready mailboxes to Q4 agencies.

    called get_warmup_status, attach_campaign_mailboxes

    Agent: 8 ready mailboxes attached. The other 4 are refused until day 14; I add them then if you want.

Prompts

Things to ask, by assistant

The same server and tools in every assistant. Each card links the setup for that assistant.

  • Start warm-up on every mailbox on getacme.info and tell me the ready date.

    Set up Claude

  • Show my mailboxes with a warm-up inbox rate under 80% this week.

    Set up ChatGPT

  • Which mailboxes are ready to send today, and how many will be ready next week?

    Set up Cursor

  • List mailboxes whose spam rate is above 5% and the domain each one is on.

    Set up Codex

  • Is warm-up running on all my mailboxes? Start it on any that are not warming.

    Set up Grok

  • Give me a table: mailbox, days warming, inbox rate, ready date.

    Set up VS Code

What the agent cannot do

  • Warm up mailboxes outside your Outreach2day workspace; no tool adds a Google, Microsoft or other mailbox
  • Stop warm-up or change its daily volume; there is no tool for either
  • Run a seed-list inbox placement test; inbox and spam rate come from the warm-up network
  • Shorten the 14 days: campaigns accept a mailbox only 14 days after warm-up starts
  • Show mailbox passwords, SMTP/IMAP logins or API keys in the chat

Pricing

  • $2.50 per mailbox a month; warm-up and sending included
  • 12 mailboxes minimum
  • Domains billed yearly: .com $13, .info $5
  • The MCP server comes with the account
  • Connecting domains you already own is free
Pricing details

Book a call

Book a 30-minute call

Talk to the team that runs the MCP server. We check your setup for your AI client 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 your AI client setup

See open times in your time zone and book on this page.

Or open the booking page

Questions

Or talk to the team

What does get_warmup_status return for each mailbox?

The warm-up state, days warming, whether the mailbox is ready, its ready date, and the inbox rate and spam rate from warm-up, plus a workspace summary: total, ready and count by state.

How long does warm-up take before a mailbox can send?

14 days. A campaign accepts a mailbox 14 days after its warm-up started, and full volume comes from day 21. Warm-up keeps running after that.

Can the MCP server warm up my Google Workspace or Outlook mailboxes?

No. Warm-up runs on mailboxes in your Outreach2day workspace: ones you ordered, or ones created on domains you connected. There is no tool to add an outside mailbox.

Does warm-up cost extra?

No. Warm-up is included in the $2.50 per mailbox a month, with 12 mailboxes minimum.

Is the warm-up inbox rate an inbox placement test?

No. It is measured on warm-up emails between mailboxes in the warm-up network. The server has no seed-list placement test; preflight_campaign checks that mailboxes are warm before a launch.

Other jobs for the same server

Each page lists the tools for the job, an example session, prompts per assistant and the limits.

Other cold email MCP servers, compared

Each vendor's official MCP server next to ours, from the vendor's own docs.

Setup

Connect your AI client

Add https://public.outreach2day.com/mcp to your AI client 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

OAuth sign-in

claude.ai, Claude Desktop and mobile

  1. In claude.ai or Claude Desktop, open Customize, Connectors, click + and choose Add custom connector
  2. Paste the server URL, https://public.outreach2day.com/mcp, and click Connect
  3. 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
  4. 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
Add to ClaudeClaude docs: add a custom connector
OAuth sign-in

ChatGPT (developer mode)

  1. Settings, Security and login: turn on Developer mode
  2. Go to chatgpt.com/plugins, click +, name the app Outreach2day, enter the server URL under Connection and create it
  3. In a new chat, add Outreach2day from the tools menu. ChatGPT opens the Outreach2day sign-in page on the first tool call; sign in and allow access
OpenAI docs: ChatGPT developer mode
OAuth sign-in

Claude Code

  1. Add the server with the command below (user scope: every project)
  2. In Claude Code, run /mcp, pick outreach2day and choose Authenticate. Or run claude mcp login outreach2day
  3. 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
  4. 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 Code docs: MCP
Terminal
claude mcp add --transport http --scope user outreach2day https://public.outreach2day.com/mcp# then, in Claude Code: /mcp, outreach2day, Authenticate
OAuth sign-in

Codex CLI

  1. Add the server with codex mcp add, or put the block in ~/.codex/config.toml
  2. Run codex mcp login outreach2day
  3. 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
  4. Run codex mcp list to check it
Codex docs: configuration reference
Terminal
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 every client on this computer with one command

curl -fsSL https://outreach2day.com/install | sh

It adds the server by URL to Claude Code, Cursor, VS Code, Windsurf, Gemini CLI and Codex, and prints the connector steps for Claude Desktop, after a backup of each config. Each client asks you to sign in to Outreach2day on first use. View the script

Warm-up from your AI assistant

Add the server URL, sign in to Outreach2day and ask. You approve every order and every launch.

Setup stepsGet API key