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.
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.
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.
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.
Create an API key in Settings → Integrations & API, then point your client at the server. That's it — the 16 tools appear automatically.
Add the server to your client's MCP configuration (for Cursor, that's ~/.cursor/mcp.json):
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.
Four groups cover the whole outbound loop — from adding leads to launching campaigns and reacting to replies.
List campaigns with status and reply stats
Get a campaign's settings, schedule and stats
Change name, limits and deliverability settings
Launch a new campaign or resume a paused one
Pause a running campaign
Change timezone, days and time windows
Permanently delete a campaign
Create or update up to 1,000 leads, straight into a campaign
Get a lead's contact and company details
Update a lead's details
Permanently delete a lead
List connected sending accounts and their status
Get one sending account
List registered webhook endpoints
Subscribe a URL to replies, bounces and more
Remove a webhook endpoint
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.
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.
Both surfaces do the same things with the same keys. Pick the one that matches how you work — or use both.
REST API
MCP server
Same keys · same scopes · same rate limits
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.
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.
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.
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.
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.
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.
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.
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.
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.
P.s. these are actually real reviews (not fake G2 reviews) 🙂

Address: 151 Calle de San Francisco San Juan, Puerto Rico
Email: support@emailchaser.com
Product
Cold Email SoftwareEmail FinderCampaignsSales CRMLead FinderEmail AccountsEmail VerifierCold Email APIMCP ServerAPI documentationComparisons
Best cold email softwareInstantly alternativesSmartlead alternativesInstantly vs EmailchaserSmartlead vs EmailchaserHunter vs EmailchaserFree tools
All free toolsBulk Email VerifierDeliverability TestEmail Header AnalyzerSMTP Settings FinderCold Email TemplatesBoolean Search BuilderName SplitterCompany Email FormatSpam Word CheckerInternational
Cold email (ES)Cold email (FR)Cold email (DE)Cold email (IT)Cold email (PT)Verifica email (IT)© Copyright 2026 Emailchaser