Emelia MCP Server
Connect Emelia to any AI assistant that speaks the Model Context Protocol (Claude, Cursor, ChatGPT...). The assistant gets 26 tools to manage your campaigns, lists and contacts, enrich and verify emails, and monitor deliverability — in plain language.
The key concept: contacts live in lists. When a list is attached to a running campaign, every contact your assistant adds to the list automatically enters the campaign.
Authentication
All connections use your Emelia API key. Find it in your Emelia account.
Remote server (recommended)
No install needed — add a custom MCP connector with:
- URL:
https://mcp.emelia.io/mcp - Header:
Authorization: <your API key>(aBearerprefix or theX-Api-Keyheader also work)
For clients configured with a JSON file (Claude Code, Cursor):
{
"mcpServers": {
"emelia": {
"type": "http",
"url": "https://mcp.emelia.io/mcp",
"headers": { "Authorization": "<your API key>" }
}
}
}
Local server via npm (coming soon)
An emelia-mcp npm package for stdio setups (npx -y emelia-mcp with an EMELIA_API_KEY environment variable) is on its way — until then, use the remote server above.
Example prompts
- "Add these 3 prospects to my SaaS founders list" — they enter the attached campaigns automatically
- "What's the reply rate of my Q3 outbound campaign this week?"
- "Find and verify the email of John Doe at Acme, then add him to my Warm leads list"
- "Do we already have jane@brands.io somewhere? Update her phone number"
- "Which of my sending accounts are disconnected or have a low warmup score?"
Some tools consume Emelia credits (email finder, phone finder, email verifier) — your assistant is told so and should warn you before using them.