Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Connect Remote server
claude mcp add --transport http mcp-server https://api.e2a.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"{
"mcpServers": {
"mcp-server": {
"url": "https://api.e2a.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}{
"servers": {
"mcp-server": {
"type": "http",
"url": "https://api.e2a.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://api.e2a.dev/mcpReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional | OAuth 2.1 is the recommended connection (add the connector and authorize — no key to paste; auto-discovered via /.well-known/oauth-protected-resource). For programmatic / self-host use, a Bearer e2a API key (e2a_acct_… or e2a_agt_…) is also accepted. |
Details
| Endpoint | https://api.e2a.dev/mcp (Streamable HTTP) |
| First published | 28 Jul 2026 |
| Last updated | 28 Jul 2026 |
| Registry name | dev.e2a/mcp-server |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.