Mailcycle vs e2a — email for AI agents
Mailcycle is an MCP server published by mailcycle.email. Marketplaces we read that list it: 1 (Official MCP Registry). e2a — email for AI agents is an MCP server published by Mnexa-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  e2a — email for AI agents | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.2 No figure published Not marked · First seen |
Listed Version: 0.3.2 Downloads/month (npm): 133 Downloads/week (npm): 18 Forks (GitHub): 27 Stars (GitHub): 194 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Mailcycle | e2a — email for AI agents |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 194 |
| Forks (GitHub) (differs) | No figure on GitHub | 27 |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | On your machine (mailcycle-mcp) | Remote server (mcp.e2a.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/mnexa-ai/e2a |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Mailcycle
An email address for your AI agent. Read, wait for and reply to mail, decrypted on your machine.
e2a — email for AI agents
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
How to run each
Mailcycle As a local MCP server: npm package
claude mcp add --transport stdio mailcycle -- npx -y mailcycle-mcpe2a — email for AI agents As a remote MCP server
claude mcp add --transport http e2a-email-for-ai-agents https://mcp.e2a.dev/mcp --header "Authorization: Bearer <YOUR_E2A_API_KEY>"Requires: E2A_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only e2a — email for AI agents has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Mailcycle publish no settings it asks for, so we do not compare settings.
What it can do: Mailcycle · What it can do: e2a — email for AI agents · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.