MCP for cold email

The cold email MCP server for AI agents

Give Claude Code, Cursor or any compatible MCP client direct, secure access to your Emailchaser workspace. Your AI agent can launch campaigns, add leads, watch replies and manage webhooks — using scoped API keys you can revoke at any time.

Emailchaser MCPconnected
Add 40 leads to my “SaaS founders” campaign and launch it.
add_leads → 40 leads added
launch_campaign → running
Done — 40 leads added and “SaaS founders” is now sending.
16AI tools
4tool groups
0installs — fully hosted
1API key to connect

The Model Context Protocol (MCP) is the open standard that lets AI assistants use real tools instead of just answering questions. The Emailchaser MCP server exposes your cold email software as 16 tools an AI agent can call: campaigns, leads, sender accounts and webhooks. It's hosted, so there's nothing to install — connect your client to the endpoint below with an API key from Settings → Integrations & API.

https://app.emailchaser.com/api/mcp

Under the hood, every tool call goes through the Emailchaser API with your key, so the same authentication, scopes and rate limits apply — an AI agent can never do more than the key you gave it allows.

How the MCP server connects

Your AI agent speaks MCP to the hosted server with your API key. The server maps each request to a tool, calls the REST API, and acts on your workspace — nothing runs on your machine.

AI agentClaude Code · CursorMCPBearer keyMCP serverapp.emailchaser.com/api/mcp · 16 toolsRESTYour workspaceCampaigns · Leads · Inboxes

Why connect an AI agent

Natural-language control

Ask in plain English — “pause my two worst campaigns” — instead of writing HTTP calls or clicking through a dashboard.

Hosted, zero setup

Nothing to install or run locally. Point your client at one URL with your API key and the tools appear automatically.

Scoped and revocable

Every action uses an API key you control. Use a read-only key for analysis, and revoke access instantly whenever you want.

Reads your live data

Tools return live campaign stats, so your agent can read reply rates, decide what to change, then act — read, reason, then do.

Connect your AI assistant in one step

Create an API key in Settings → Integrations & API, then point your client at the server. That's it — the 16 tools appear automatically.

Claude Code

Terminal
claude mcp add --transport http emailchaser https://app.emailchaser.com/api/mcp \
--header "Authorization: Bearer YOUR_API_KEY"

Cursor and other MCP clients

Add the server to your client's MCP configuration (for Cursor, that's ~/.cursor/mcp.json):

~/.cursor/mcp.json
{
"mcpServers": {
"emailchaser": {
"url": "https://app.emailchaser.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}

Any MCP client that supports remote servers over Streamable HTTP with custom headers works the same way: server URL plus your API key as a Bearer token in the Authorization header.

16 tools for running outbound with AI

Four groups cover the whole outbound loop — from adding leads to launching campaigns and reacting to replies.

Campaigns
  • list_campaigns

    List campaigns with status and reply stats

  • get_campaign

    Get a campaign's settings, schedule and stats

  • update_campaign

    Change name, limits and deliverability settings

  • launch_campaign

    Launch a new campaign or resume a paused one

  • pause_campaign

    Pause a running campaign

  • update_campaign_schedule

    Change timezone, days and time windows

  • delete_campaign

    Permanently delete a campaign

Leads
  • add_leads

    Create or update up to 1,000 leads, straight into a campaign

  • get_lead

    Get a lead's contact and company details

  • update_lead

    Update a lead's details

  • delete_lead

    Permanently delete a lead

Sender emails
  • list_sender_emails

    List connected sending accounts and their status

  • get_sender_email

    Get one sending account

Webhooks
  • list_webhooks

    List registered webhook endpoints

  • create_webhook

    Subscribe a URL to replies, bounces and more

  • delete_webhook

    Remove a webhook endpoint

What you can ask your AI agent to do

Because the tools return live campaign stats, your agent can combine them: read reply rates with list_campaigns, decide what to change, then act with pause_campaign or update_campaign_schedule.

Secure by design

Giving an agent access should never mean giving up control. Every connection is scoped to a key you own and can pull back instantly.

Your key, your scope

Connect with a read-only or read & write key. A read-only key can analyze and report, but never change anything.

Revoke any time

Delete a key in Settings → Integrations & API and the agent loses access immediately — every call is authenticated with that key.

Annotated tools

Read-only tools are marked safe and delete tools destructive, so MCP clients can run reads freely and prompt you before actions that change your data.

Same limits as the API

Every call runs through the REST API with the same authentication and rate limits, so an agent can never exceed them.

API or MCP — same power, two front doors

Both surfaces do the same things with the same keys. Pick the one that matches how you work — or use both.

REST API

Built forYour product, scripts and no-code tools
InterfaceHTTP requests and JSON
Best whenYou're writing code or wiring automations
Explore the API

MCP server

Built forAI agents like Claude Code and Cursor
InterfaceNatural language, mapped to tools
Best whenYou want an assistant to run outbound
You're on the MCP page

Same keys · same scopes · same rate limits

MCP server FAQ

What is an MCP server?

MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude securely use external tools. An MCP server exposes a set of tools — in Emailchaser's case, tools for managing cold email campaigns, leads, sender accounts and webhooks — that an AI agent can call on your behalf, with your permission.

What can an AI agent do with the Emailchaser MCP server?

Anything the tools allow: list and analyze campaigns, launch or pause sending, update schedules and settings, add up to 1,000 leads at a time, inspect sender email accounts, and manage webhooks. You stay in control — read-only tools are marked safe and the delete tools are marked destructive, so MCP clients can run reads freely and prompt you before anything that changes your data.

Which AI tools can connect to it?

Any MCP client that supports remote servers over Streamable HTTP with custom headers, including Claude Code, Claude's developer platform and Cursor. You add the server URL and pass your Emailchaser API key in the Authorization header.

Is it safe to give an AI access to my cold email account?

The MCP server only works with an API key you create, scoped to one workspace. Create a read-only key if you just want analysis and reporting, and revoke any key instantly from Settings → Integrations & API. Every call is subject to the same authentication and rate limits as the regular API, and destructive tools are flagged so MCP clients can prompt before using them.

Do read-only keys really block changes?

Yes. Connect with a read-only key and the agent can call the list and get tools but not the create, update, launch, pause or delete tools — the backend rejects any write attempt, so the agent simply gets an error instead of modifying your data.

Is my data sent to an AI provider?

The MCP server returns tool results to whichever MCP client you connect — for example Claude Code. Whatever model that client uses will see those results, exactly as it would see any other context you give it. Connect only clients you trust, and use a read-only key when you just need analysis.

Do I need to install anything to use it?

No. The Emailchaser MCP server is hosted — there is no npm package to install or process to run locally. Point your MCP client at the server URL with your API key and the tools appear automatically.

How do I revoke access?

Delete the API key in Settings → Integrations & API. Because every MCP call is authenticated with that key, the connection stops working the moment the key is removed.

How is the MCP server different from the API?

They expose the same capabilities. The REST API is for code — your product, scripts or no-code tools making HTTP calls. The MCP server wraps that same API so AI agents can use it through natural language. Same keys, same scopes, same rate limits.

Still not convinced?

Read dozens of customer reviews.

SEE REVIEWS

P.s. these are actually real reviews (not fake G2 reviews) 🙂

Customer reviews

Ready to 10x your pipeline?

Send your first cold email campaign today, risk-free.

Try for free