Ext Ops Panel
Open dashboard
Comparison

email-triage vs Command Mail

email-triage is a plugin bundle for AI coding tools published by Context-Link. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Command Mail is an MCP server published by commandmail.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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-triageCommand Mail
Claude Code: claude-plugins-community Listed
Version: 1.1.3
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 0
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-triage vs Command Mail
Factemail-triageCommand Mail
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (commandmail.app/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/context-link/email-triage-plugingithub.com/fyn-labs/commandmail-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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-triage

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

Triage your support inbox from Claude. Pull unread emails, generate context-aware draft replies using your knowledge base, and review them in an interactive UI, ready for a human to copy, edit, and send.

Command Mail

In its own words, on Official MCP Registry:

One inbox for all your addresses: your AI agent reads, sorts, drafts and sends with your permission.

How to run each

email-triage

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Command Mail As a remote MCP server

Claude Code
claude mcp add --transport http mail https://commandmail.app/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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-triage · What it can do: Command Mail · 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