E2a — Email For AI Agents
A solo builder uses this tool to give AI agents the ability to send authenticated emails with human-in-the-loop approval and verification.
Overview
e2a MCP is a MCP server for the Build phase that provides authenticated, SPF/DKIM-oriented email inboxes and sending for AI agents with optional human approval.
What is this MCP server?
- Per-agent email inboxes for isolated communication
- HITL approval gates to prevent unwanted agent actions
- SPF/DKIM verified to ensure deliverability
- Server/package version 0.3.2
- Remote MCP URL: https://mcp.e2a.dev/mcp (streamable-http)
- npm package: @e2a/mcp-server
Community signal: 156 GitHub stars.
What problem does it solve?
Your agents need to send and receive email safely, but raw SMTP or personal inboxes lack per-agent identity, verification, and approval guardrails.
Who is it for?
Indie builders launching agent products that must email users with verified domains and optional HITL on outbound messages.
Skip if: Simple newsletter campaigns or teams that only need a static transactional provider with no agent inbox model.
What do I get? / Deliverables
After you connect e2a with an API key or OAuth token, agents can use dedicated inboxes and governed send paths through MCP instead of improvised mail hacks.
- MCP-accessible agent inboxes and governed outbound email
- Integration path for verified domain sending with approval workflows
Recommended MCP Servers
Journey fit
This tool belongs in the build phase because it's a backend integration that enables core functionality for agent-based applications. It fits integrations because it provides authenticated email gateway capabilities that agents need to communicate externally with SPF/DKIM verification.
How it compares
Agent-native email gateway MCP, not a marketing automation suite or generic scraping utility.
Common Questions / FAQ
Who is e2a MCP for?
e2a MCP is for solo builders and small teams running AI agents that need real email inboxes, authenticated sending, and optional human approval before messages go out.
When should I use e2a MCP?
Use it during Build when you integrate agent-driven support, notifications, or workflows that must send email from verified agent identities rather than shared personal accounts.
How do I add e2a MCP to my agent?
Use https://mcp.e2a.dev/mcp with Authorization Bearer and your e2a API key or OAuth token, or install @e2a/mcp-server and set E2A_API_KEY (and optional E2A_AGENT_EMAIL) for stdio MCP.