Connect the MCP server

The Emelia MCP server lets an AI assistant work in your Emelia account in plain language: "add these three prospects to my SaaS founders list", "what is the reply rate of my Q4 campaign this week?", "draft a reply to the last email from Nexora".

It covers the whole Emelia API except the legacy campaigns: 82 tools for campaigns and their sequences, lists and contacts, enrichment, LinkedIn extractions, sending mailboxes and your account. Once the Inbox is set up, 61 more tools read, sort and answer the emails of your inbox. That makes 143 tools, in 8 categories you can turn on one by one.

Most clients sign you in with your Emelia account the first time they connect: you add the URL, an Emelia page opens in your browser, and you click Authorize. There is nothing to copy. An API key is only needed for scripts, CI, and clients that cannot sign in.

Whatever the client, name the server emelia: the tools then show up as mcp__emelia__<tool>, the names the Claude Code plugin expects.

InstallCopy Anchor Link

Claude loads the tools it needs on demand: in Claude Code, Claude Desktop and claude.ai, connect the plain URL and keep every tool. Cursor, VS Code and most other clients send the description of every tool to the model with each message, and some cap the number of tools: give them only the categories you need, with ?toolsets=.

claude mcp add --transport http --scope user emelia https://mcp.emelia.io/mcp

{
  "mcpServers": {
    "emelia": {
      "type": "http",
      "url": "https://mcp.emelia.io/mcp"
    }
  }
}

claude mcp add --transport http --scope user emelia https://mcp.emelia.io/mcp \
  --header "Authorization: YOUR_EMELIA_API_KEY"

AuthenticationCopy Anchor Link

Sign in with your Emelia accountCopy Anchor Link

The first time it connects, the client opens an Emelia page in your browser. Sign in to Emelia if needed, check the account shown on the page, and click Authorize: you are sent back to the client, connected. The page waits 10 minutes; after that, start the connection again from the client.

The assistant then acts as you, as it would with an API key: it reads and changes your campaigns, lists, contacts and mailboxes, sends emails and spends your credits, within the same per minute quota. The inbox tools work the same way.

The access lasts 30 days, and most clients renew it on their own: they stay connected as long as you use them at least once every 180 days. A client that does not renew it asks you to sign in again after 30 days.

To see the assistants connected to your account, or to cut the access of one of them, open Settings, API & Webhooks, Connected apps in the Emelia app and click Disconnect. The assistant loses access within 30 seconds.

With an API keyCopy Anchor Link

An API key suits scripts, CI, a machine without a browser, or a client that cannot sign in with OAuth. Pass it in the Authorization header (raw or Bearer <key>), or in X-Api-Key. With a key, the client does not ask you to sign in.

The inbox toolsCopy Anchor Link

The 61 tools of the inbox and inbox_settings categories work on the Inbox of your Emelia account: they read, sort and answer its emails, and manage its labels, views and rules.

They appear only once the Inbox has been opened in Emelia. The server creates nothing for you: on an account that never opened it, the server lists the 82 Emelia tools, with no error. Open the Inbox tab of the Emelia app once, wait a few minutes, then reconnect the server in your client.

The links these tools return open the email or the draft in the Emelia inbox, at https://v3.emelia.io/inbox.

Check the connectionCopy Anchor Link

To check the server and your key by hand, list the tools:

curl -s https://mcp.emelia.io/mcp \
  -H "Authorization: $EMELIA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

With ?toolsets=, only the tools of those categories come back:

curl -s "https://mcp.emelia.io/mcp?toolsets=campaigns,inbox" \
  -H "Authorization: $EMELIA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A wrong key still lists the Emelia tools: the key is checked at the first tool call. A misspelled category gets an HTTP 400 that lists the valid ones. Without a key, the server answers 401 with the WWW-Authenticate header that starts the sign-in in OAuth clients.