Ext Ops Panel
Open dashboard
Comparison

email-assistant vs e2a — email for AI agents

email-assistant is a plugin bundle for AI coding tools published by marian-kamenistak. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). e2a — email for AI agents is an MCP server published by e2a.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplaceemail-assistante2a — email for AI agents
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 27
Stars (GitHub): 199
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

email-assistant vs e2a — email for AI agents
Factemail-assistante2a — email for AI agents
Marketplaces that list it11
Stars (GitHub) (differs)3 (worse)199 (better)
Forks (GitHub) (differs)0 (worse)27 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.e2a.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/marian-kamenistak/claude-email-assistantgithub.com/tokencanopy/e2a
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 31 h ago returned HTTP 405

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

email-assistant

In its own words, on Claude Code: claude-plugins-community:

Autonomous email triage and reply system. Drafts replies in your voice, saves as Gmail drafts, and learns from your corrections.

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.

How to run each

email-assistant As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install email-assistant@claude-community

e2a — email for AI agents As a remote MCP server

Claude Code
claude mcp add --transport http e2a-email-for-ai-agents https://api.e2a.dev/mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: email-assistant · What it can do: e2a — email for AI agents · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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