Command Mail vs send0
Command Mail is an MCP server published by commandmail.app. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). send0 is an MCP server published by send0-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  Command Mail |  send0 |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.1 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
| Fact | Command Mail | send0 |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (commandmail.app/mcp) | Remote server (api.send0.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/fyn-labs/commandmail-plugin | github.com/send0-dev/send0-v2 |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | Responded 7 h ago | not 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
Command Mail
One inbox for all your addresses: your AI agent reads, sorts, drafts and sends with your permission.
send0
Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.
How to run each
Command Mail As a remote MCP server
claude mcp add --transport http mail https://commandmail.app/mcpsend0 As a remote MCP server
claude mcp add --transport http send0 https://api.send0.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: SEND0_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Command Mail 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 Command Mail publish no settings it asks for, so we do not compare settings.
What it can do: Command Mail · What it can do: send0 · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.