← Back to directory

e2a MCP Server

Community

Authenticated email gateway for AI agents

GitHub source repository ↗

★ 184 Stars Category · Dev Tools Popular Source revision e1f8b1839b38

42FMRS · D

Reliability

4/20

Security and permissions

5/20

Maintenance

8/20

Documentation

13/20

Setup experience

12/20

The e2a MCP server provides a feature-rich email gateway for AI agents, with authenticated inbound/outbound, HITL review, content screening, and multiple delivery channels. Ideal for AI agent projects needing reliable email communication.

Read the FMRS scoring method →

e2a is an authenticated email gateway for AI agents. It receives inbound email, evaluates SPF, every DKIM signature, and DMARC, and delivers structured authentication evidence over webhooks, WebSocket, REST, or MCP. Outbound goes through an HTTP API with an optional human-in-the-loop approval gate.

Tools

list_messages

List messages in an agent's mailbox

get_message

Get detailed information about a specific message

get_attachment

Retrieve an attachment from a message

list_conversations

List conversations in an agent's mailbox

get_conversation

Get details of a specific conversation

update_message_labels

Update labels on a message

send_message

Send a new email as the agent

reply_to_message

Reply to an existing message while preserving thread structure

forward_message

Forward an existing message

list_reviews

List review items pending human approval

get_review

Get details of a specific review item

approve_review

Approve a pending review item

reject_review

Reject a pending review item

create_webhook

Create a webhook subscription to receive inbound email events

Setup

For Claude Code: run claude plugin marketplace add tokencanopy/e2a and claude plugin install e2a@e2a. For Cursor: add { "mcpServers": { "e2a": { "url": "https://api.e2a.dev/mcp" } } } to .cursor/mcp.json. For other MCP clients, point directly to https://api.e2a.dev/mcp. On first use, a browser opens for OAuth authorization; no API key paste required.

Fit and risk

Best for

Developers building AI agents that need to communicate with humans or other agents
Teams that need to receive email from behind firewalls or on laptops without public URLs
Use cases requiring authenticated email delivery (SPF/DKIM/DMARC)
Organizations that want to review outbound email before sending

Not for

Users who need a full MTA like Postfix or Postal
Users who only need simple email sending without external dependencies
Scenarios requiring advanced deliverability management like bounce handling and analytics

Required permissions

Read and send email
Manage agents, domains, and webhooks
Manage human approvals (approve/reject)
Requires API key or OAuth authorization
Requires DNS TXT verification for custom domains

Risks and side effects

Misuse of API keys could lead to unauthorized email access
Inbound emails may contain prompt injection or phishing attempts
Improper webhook signature verification could be spoofed
Dependency on external service availability

Troubleshooting

Check that the API key is correctly set in the E2A_API_KEY environment variable
Ensure network access to api.e2a.dev
When verifying webhook signatures, use the correct whsec_ secret
Verify the agent mailbox exists and has proper permissions
Check HTTP status codes in server responses to debug errors

Use cases

Give AI agents a real email address

Receive inbound email without a public URL via WebSocket/REST/MCP

Stream authenticated email events via webhook or WebSocket

Send and reply to emails via API or MCP tools

Implement human-in-the-loop approval for critical emails

Scan inbound emails for prompt injection and phishing

Supported clients

Claude DesktopFull support

CursorFull support

ClineFull support

Google ADKFull support

LangChainFull support

OpenAI Agents SDKFull support

ZedFull support

GooseFull support

WindsurfFull support

Related MCP servers

Compare with other MCP servers