Connecting Evermail to Claude
Evermail runs a remote MCP server, so Claude can search, read, and export your archive directly inside a conversation — no copy-pasting emails back and forth.
What you need
The MCP integration is available on Starter, Pro, Team, and Enterprise plans — Free-tier accounts can't connect. See Billing & Plans to upgrade.
That's it. The browser and Claude Code methods below use sign-in with your Evermail account — no API key required. Each person who connects signs in as themselves, and access can be revoked per person. An API key is only needed for the raw-JSON method at the bottom, and you can create one at app.evermail.ai/settings/integrations (click Create API key; the value starting with em_live_ is only shown once).
Claude web or desktop app — one-click sign-in
No API key, no terminal. Claude detects that Evermail signs you in and walks you through it. Every teammate connects with their own Evermail identity.
Add the connector
The path depends on your Claude plan:
- Free, Pro, or Max: go to Customize → Connectors, click Add custom connector, and paste
https://mcp.evermail.ai/mcp. - Team or Enterprise: an account Owner adds it once under Organization settings → Connectors: click Add, then Custom (choose Web if Claude asks for a type), and paste
https://mcp.evermail.ai/mcp. Teammates then connect it from Customize → Connectors.
If Claude's dialog asks how people sign in, keep the detected OAuth setting — that's Evermail's sign-in. Free Claude accounts are limited to one custom connector in total.
Sign in and approve
Click Connect on the evermail connector. A browser window opens the Evermail sign-in, then asks "Claude wants to access your Evermail archive" — click Allow access. That's the whole flow: no API key to create or paste, and the access is tied to your account, not a shared secret.
Turn it on in a conversation
Connectors are enabled per conversation. Click the + button in the chat box, open Connectors, and switch on evermail. Then try one of the example prompts below.
Came here because a shared API key felt wrong? This method replaces it: each person signs in as themselves, you can cut one person's access without rotating anything, and Claude re-asks for sign-in if an authorization lapses. The older header-key method below still works if you specifically want a shared credential.
Claude Code
Sign-in works here too — add the server, then authenticate once from the /mcp panel.
Add the Evermail MCP server
Run this in your terminal:
claude mcp add --transport http evermail https://mcp.evermail.ai/mcpSign in
Run claude mcp login evermail (or open the /mcp panel inside Claude Code and choose Authenticate). Your browser opens the Evermail sign-in and the Allow access screen, and Claude Code picks the connection up automatically.
Confirm it's connected
Run claude mcp list — you should see evermail listed as connected. Then just ask Claude to search your archive; see example prompts below.
Optional: make it available everywhere. By default the server is only added to the current project. Add --scope user to the add command to make it available in every project on your machine.
Claude desktop or web with a shared API key
One credential shared by everyone. Claude's Request headers feature is in beta and rolling out gradually — it may not be on your account.
Prefer the sign-in method above unless you specifically want one shared key. This method needs a Request headers section in Claude's connector dialog; if it isn't there, use the sign-in method — it isn't gated.
Open connector settings
The path depends on your Claude plan:
- Free, Pro, or Max: go to Customize → Connectors, then click Add custom connector.
- Team or Enterprise: an account Owner must go to Organization settings → Connectors, select Add, then Custom. If Claude asks for a connector type, choose Web. Teammates then connect it from Customize → Connectors.
Free accounts are limited to one custom connector in total.
Enter the server URL
Paste https://mcp.evermail.ai/mcp as the connector URL.
Add the API key as a request header
Open the Request headers section and add a header named x-api-key, with your Evermail key as the value. Paste the key exactly as you copied it, including the em_live_ prefix — Claude sends the value verbatim and doesn't add a scheme or prefix of its own.
Claude won't show the value again after you save it, so keep your copy until you've confirmed the connection works.
Turn it on in a conversation
Connectors are enabled per conversation. Click the + button in the chat box, open Connectors, and switch on evermail. Then try one of the example prompts below.
One credential, shared. A connector header is entered once and shared by everyone using that connector, so all of them read the archive through the same Evermail key and we see one identity rather than each person's. If you need each teammate to sign in as themselves, use the sign-in method at the top.
Raw JSON config
If your tool accepts a raw mcpServers block instead of a UI flow, use this:
{
"mcpServers": {
"evermail": {
"type": "http",
"url": "https://mcp.evermail.ai/mcp",
"headers": { "X-API-Key": "em_live_your_key_here" }
}
}
}The "type": "http" line matters — without it, Claude Code treats the entry as a local stdio server and silently skips it.
What you can then ask Claude
Once connected, Claude can call Evermail's search, read, and export tools directly. A few things to try:
| "Search my archive for the 2019 Henderson contract" |
| "Export everything from john@acme.com in Q3 2020" |
| "Find every email from our old accountant and summarize what they were chasing" |
| "List my saved searches, then run the one called 'invoices'" |
Common errors
| Error | What it means |
|---|---|
401 Unauthorized | With a shared-key connection: the API key is missing, wrong, or has been revoked. Create a fresh key at Settings → Integrations. With a sign-in connection: the authorization expired — click Connect on the evermail connector and sign in again. |
403 Forbidden | The account is on the Free plan, which can't connect. Upgrade on Settings → Billing (Starter or above includes MCP), then reconnect. |
404 Not Found | The URL is wrong. It must be exactly https://mcp.evermail.ai/mcp — no trailing slash, no other path, and not /sse (Evermail's MCP server doesn't support the legacy SSE transport). |
429 Too Many Requests | You've hit the rate limit of 20 requests per minute per IP address. Wait a minute and try again. |
What a connection can do
Whether Claude connects by signing in or with an API key, the access is the same: full read access to your workspace's entire archive — anything you or a teammate could search or open in the Evermail app, Claude can too.
With the sign-in method, the access is tied to the individual Evermail account that approved it, and Claude keeps it until that authorization expires or is revoked — Claude re-asks for sign-in when that happens. With an API key, treat the key like a password: don't share it or commit it to a repository. You can revoke a key at any time from Settings → Integrations, which immediately cuts off access for anything using it.
Evermail only sends the specific emails Claude requests through a tool call, in that conversation. What Anthropic does with data sent to Claude is governed by Anthropic's own privacy policy, not Evermail's.
Common questions
Which tools does the Evermail MCP server expose?
search_emails, get_email, list_mailboxes, get_mailbox, list_saved_searches, create_saved_search, export_emails, get_profile, and get_archive_analytics. Claude picks the right one automatically based on what you ask.Can Claude write or delete anything in my archive?
Does this work with ChatGPT or other assistants?
Is my data used to train Claude?
Ready to connect Claude?
Add the connector, sign in with Evermail, and you're done — no API key needed.
Open Claude's connectors →