Add e2a to Communication section

[jiashuoz]

What

Adds e2a to the Communication section, between marlinjai/email-mcp and multimail-dev/mcp-server.

Why this entry

e2a is an authenticated email gateway built specifically for AI agents — not a wrapper around an existing user mailbox like Gmail/IMAP-based servers, and not a CRM like marketing-email platforms. Each agent gets its own deliverable email address on a shared or custom domain, inbound mail arrives SPF/DKIM-verified, and outbound can be gated behind human-in-the-loop approval.

Icons rationale

• 📇 TypeScript (the MCP server)
• ☁️ Cloud — hosted at mcp.e2a.dev (Streamable HTTP + OAuth 2.1 / API key Bearer)
• 🏠 Local — self-hostable; backend (Go) at github.com/Mnexa-AI/e2a
• 🍎 🪟 🐧 — stdio path via npx -y @e2a/mcp-server works on all three

Links

• Repo: https://github.com/Mnexa-AI/e2a
• MCP server source: https://github.com/Mnexa-AI/e2a/tree/main/mcp
• npm: https://www.npmjs.com/package/@e2a/mcp-server
• Hosted: https://mcp.e2a.dev/mcp
• Docs: https://e2a.dev

[github-actions]

Hey,

To ensure that only working servers are listed, we're updating our listing requirements.

Please complete the following steps:

1. Ensure your server is listed on Glama. If it isn't already, submit it at https://glama.ai/mcp/servers and verify that it passes all checks (note: you must add Dockerfile directly to Glama. For checks to pass, we only need the server to start and respond to introspection requests).

2. Update your PR by adding a Glama score badge after the server description, using this format:

[![OWNER/REPO MCP server](https://glama.ai/mcp/servers/OWNER/REPO/badges/score.svg)](https://glama.ai/mcp/servers/OWNER/REPO)

Replace OWNER/REPO with your server's Glama path.

If you need any assistance, feel free to ask questions here or on Discord.

P.S. If your server already has a hosted endpoint, you can also list it under https://glama.ai/mcp/connectors.