Skip to content
RRAECHLY

Model Context Protocol · Streamable HTTP

The whole product, as tools.

Raechly exposes all 147 of its capabilities over MCP. Not a reporting subset. Your assistant orders your sending domain, finds the people a campaign should reach, writes the emails, shows them to you for approval, works the inbox and reads the send log with the errors intact.

Connect
claude mcp add --transport http raechly \
  https://mcp.raechly.com/mcp \
  --header "Authorization: Bearer rk_your_key"

No key yet? Add the server without the header. Claude, ChatGPT and Cursor open a sign-in page that also creates the account; Claude Code and scripts use the key from Settings.

A full setup, in one message

The reason all 147 tools matter is that setup is the hard part, and setup is exactly what most integrations leave out.

You say

Order my sending domain, find heads of marketing at D2C brands in Germany and draft a three-step campaign for them. Show me the emails before anything sends.

It runs

  1. 1. domain_ideas → names that are free
  2. 2. order_senders → Raechly buys and warms it
  3. 3. create_campaign → draft
  4. 4. set_campaign_icp → a count and examples
  5. 5. confirm_campaign_icp → once you say yes
  6. 6. review_campaign_emails
  7. 7. approve_campaign → once you say yes

117 tools, by area

Account

Files

Knowledge base

Domains

Mailboxes

sender_plan

read

What this organization's plan includes for sending: included domains and senders that Raechly buys, sets up and warms, how many it has set up so far (managed), open_orders, can_order (a domain is left to order), paid (false during a trial: the domain is bought after the first payment) and own_senders (Business: may bring its own domains and inboxes).

set_extra_domains

Ask for a different number of extra sending domains (three senders each, $25 a month each) on a paid plan.

domain_ideas

read

Lookalike .com domains for the organization's senders, built from its website (tryacme.com, acmehq.com), each with available true (free to buy), false (taken) or null (couldn't check).

list_ready_domains

read

Ready domains the organization can buy now: sending domains Raechly has warmed for about 3 weeks, so they send today instead of after a new domain's warmup.

order_senders

Order the domain the plan includes, with up to 3 senders on it.

list_sender_orders

read

The organization's sender orders: open (waiting for Raechly, or for payment of a ready domain), done (set up or handed over) or canceled.

cancel_sender_order

Cancel an open sender order before Raechly sets it up, or a ready domain that isn't paid for yet (it goes back on sale).

list_mailboxes

read

List mailboxes with warmup status, daily limits, sent-today counts and reply capture.

connect_mailbox

Connect the user's own inbox with an APP PASSWORD (Gmail: 2-step verification on, then Google Account → Security → App passwords).

create_mailbox

Business plan: create a sender on your own verified domain, with reply capture wired up automatically.

sync_replies

Read a connected mailbox's inbox now (the server also polls every 15 minutes and before each hourly send pass).

reconcile_reply_capture

Ensure every active mailbox has a working inbound routing rule — sends are gated on it.

check_reply_capture

read

Why an outbound SES mailbox can or can't send: for each one (or mailbox_id), whether its replies reach Raechly and, when they don't, a title, the reason, recommended steps in order (each with an action: open a link, setup = reconcile_reply_capture, check = this tool again, connect = connect_mailbox with an app password (username = the account that owns an alias), add_domain = create_domain, product_email = set_mailbox_purpose lifecycle) and alternatives, most likely first.

delete_mailbox

Remove a sender.

update_mailbox

Rename a mailbox's sender name (what recipients see next to the address) or change its daily limit.

Warmup

Contacts

Companies

Finding contacts

Campaigns

list_campaigns

read

List campaigns with status and send-window settings.

get_campaign

read

Get one campaign with its full step sequence and per-status lead counts.

generate_campaign

Draft a campaign with AI from a brief: name, send window and 3 to 4 steps.

create_campaign

Create a campaign with its full step sequence, send window and daily cap.

update_campaign

Change a campaign's settings: name, status, send window and days, timezone, daily limit, brief, goal, booking URL, AI instructions, protection (auto-pause on bounce rate or after N unanswered steps), exclusions (lists, tags, people active or completed elsewhere), approval, and the per-company rules (max people per company, spacing days, which reply intents pause the whole company), whether emails end with an Unsubscribe link, and which senders it sends from.

preview_email

Render one contact's email for a step exactly as it would send: variables filled, opt-out link in place.

send_test_email

Send one step to an address the user owns (one of their mailboxes, or their login email) from one of their mailboxes.

get_campaign_stats

read

A campaign's numbers, counted in the database: journey (enrolled, by status, unsubscribed), engagement (sent, failed, replied by intent, bounced, rates), the next seven days of scheduled sends, the per-step table and how many drafts await approval.

list_campaign_events

read

The campaign's own log: lifecycle changes, each send pass, AI drafting, user actions and system protection (auto-pause).

pause_contact

Pause one person's sequence in a campaign.

resume_contact

Resume a paused person; their next step is due at once (inside the send window).

remove_contact

Take a person out of a campaign.

list_drafts

read

Autopilot drafts for a campaign, pending by default: who it goes to, the step, subject and body.

approve_draft

Approve a draft so the next send pass delivers it.

reject_draft

Reject a draft with a reason; the next send pass rewrites it, told what was wrong.

replace_campaign_steps

Replace the whole sequence of a campaign.

set_campaign_status

Activate, pause or complete a campaign.

delete_campaign

Delete a campaign that never sent an email, for good: its steps, people, drafts, logs and search go with it; the contacts stay.

review_campaign_emails

read

The real emails each person in a campaign will get, a page at a time: every step's subject and body filled in for them, signed by their sender, with the unsubscribe footer.

edit_campaign_email

Change one person's email for one step, from review_campaign_emails (contact_id and step_id).

approve_campaign

The user's approval of the emails review_campaign_emails showed.

recheck_campaign_addresses

Check again the address of everyone the campaign hasn't emailed yet, as if never checked, and put back people taken out for a bad address so the check decides again (people the user removed stay out).

enroll_contacts

Enroll leads into a campaign, assigning mailboxes round-robin and scheduling the first send.

list_campaign_contacts

read

People enrolled in a campaign with their email, step, status, sender and next send time.

trigger_send

Raechly staff only: run the send pipeline now, instead of waiting for the hourly run.

Inbox

Pipeline

Results

Billing

The server has 30 more, for a feature in private beta. They aren’t listed yet.

Why the setup tools matter more than the reporting tools

Several cold email platforms now publish MCP servers, and most of them are good at the same thing: reading campaign stats and managing leads. That is genuinely useful, and it is also the easy half.

The half that costs people weeks is everything around the campaign: a sending domain, warm senders, reply capture, and working out why nothing is going out. Raechly sets up the domain and warms the senders for you, and every step is still a tool. The assistant that writes your sequence can also tell you which sender is still warming and the day it reaches full volume.

If you are comparing MCP surfaces, count what you can accomplish end to end rather than the number of tools. Ours is 147 because every screen in the dashboard has a tool behind it. See how that stacks up against Smartlead and Instantly, both of which ship their own.

MCP questions

What is an MCP server for cold email?

The Model Context Protocol is an open standard from Anthropic that lets an AI assistant call external tools. A cold email MCP server exposes your sending platform as tools the assistant can invoke, so you describe what you want in plain language instead of clicking through an interface.

Which clients can connect to the Raechly MCP server?

Anything that speaks Streamable HTTP MCP, including Claude, ChatGPT, Claude Code, Cursor and VS Code. Claude, ChatGPT and Cursor sign you in with OAuth. Claude Code and scripts send an API key from Settings › API keys in the Authorization header.

Is my API key sent to Anthropic?

No. The key is held by your MCP client and sent to the Raechly MCP server as a bearer token, which forwards it to the Raechly API. It is the tenant boundary: the API resolves your organization from the key.

Do I need an account before I connect?

No. Add the server without a key and Claude, ChatGPT or Cursor opens a sign-in page that also creates the account. Nothing works without signing in.

Can the assistant send email without me approving it?

Tool calls follow your client’s approval settings, and the destructive tools are annotated so clients can prompt before running them. Beyond that, the same server-side guardrails apply to every path: send windows, daily caps and the reply-capture gate do not care whether a human or an assistant made the call.

Add the server and sign in.

Sign in from Claude or Cursor with OAuth, or paste an organization key, and every tool appears in the conversation.