Ext Ops Panel
Open dashboard
Comparison

email-triage vs Mails.ai — Agent Email

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). Mails.ai — Agent Email is an MCP server published by mails.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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-triageMails.ai — Agent Email
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.4.0
Downloads/month (npm): 1 182
Downloads/week (npm): 393
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 Mails.ai — Agent Email
Factemail-triageMails.ai — Agent Email
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleRemote server (api.mails.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/context-link/email-triage-pluginNot stated
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 h ago, requires a key

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.

Mails.ai — Agent Email

In its own words, on Official MCP Registry:

A real inbox for AI agents: send, receive and thread email, behind a prompt-injection firewall.

How to run each

email-triage As a Claude Code plugin

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

Mails.ai — Agent Email As a remote MCP server

Claude Code
claude mcp add --transport http agent-email https://api.mails.ai/mcp

Requires: MAILS_API_KEY (secret)

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

Only Mails.ai — Agent Email 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 email-triage publish no settings it asks for, so we do not compare settings.

What it can do: email-triage · What it can do: Mails.ai — Agent Email · 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