Ext Ops Panel
Open dashboard
Comparison

e2a — email for AI agents vs io.github.joansongjr/clawaimail

e2a — email for AI agents is an MCP server published by Mnexa-AI. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.joansongjr/clawaimail is an MCP server published by joansongjr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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

Where each is published
Marketplacee2a — email for AI agentsio.github.joansongjr/clawaimail
Official MCP Registry Listed
Version: 0.3.2
Downloads/month (npm): 103
Downloads/week (npm): 21
Forks (GitHub): 27
Stars (GitHub): 194
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 136
Downloads/week (npm): 15
Forks (GitHub): 0
Stars (GitHub): 2
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

e2a — email for AI agents vs io.github.joansongjr/clawaimail
Facte2a — email for AI agentsio.github.joansongjr/clawaimail
Marketplaces that list it11
Stars (GitHub) (differs)194 (better)2 (worse)
Forks (GitHub) (differs)27 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.e2a.dev/mcp)On your machine (clawaimail-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/mnexa-ai/e2agithub.com/joansongjr/clawaimail
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 days agono remote endpoint we check

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

e2a — email for AI agents

In its own words, on Official MCP Registry:

Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.

io.github.joansongjr/clawaimail

In its own words, on Official MCP Registry:

Email infrastructure for AI agents. Create inboxes, send/receive email, and search messages.

How to run each

e2a — email for AI agents As a remote MCP server

Claude Code
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

io.github.joansongjr/clawaimail As a local MCP server: npm package

Claude Code
claude mcp add --env "CLAWAIMAIL_API_KEY=<YOUR_CLAWAIMAIL_API_KEY>" --transport stdio clawaimail -- npx -y clawaimail-mcp

Requires: CLAWAIMAIL_API_KEY (secret)

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

Only e2a — email for AI agents asks for

  • E2A_AGENT_EMAIL
  • E2A_API_KEY (secret)
  • E2A_BASE_URL

Only io.github.joansongjr/clawaimail asks for

  • CLAWAIMAIL_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: e2a — email for AI agents · What it can do: io.github.joansongjr/clawaimail · 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.

Where the data comes from: how the catalog is built