Assistant Mail MCP vs AgentiSend
Assistant Mail MCP is an MCP server published by AssistantMail. Marketplaces we read that list it: 1 (Official MCP Registry). AgentiSend is an MCP server published by fortuneflick. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  Assistant Mail MCP |  AgentiSend |
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.1 Downloads/month (npm): 257 Downloads/week (npm): 38 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (npm): 814 Downloads/week (npm): 34 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 | Assistant Mail MCP | AgentiSend |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@assistantmail/assistantmail-mcp) | Remote server (api.agentisend.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/assistantmail/assistantmail-mcp | github.com/fortuneflick/agentisend-claude-plugin |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 25 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
Assistant Mail MCP
Agent email with allowlist and consent via AssistantMail.
AgentiSend
Transactional email API for AI agents: verified domains, a per-sender budget, and a kill switch.
How to run each
Assistant Mail MCP As a local MCP server: npm package
claude mcp add --env "ASSISTANT_MAIL_API_KEY=<YOUR_ASSISTANT_MAIL_API_KEY>" --transport stdio assistantmail-mcp -- npx -y @assistantmail/assistantmail-mcpRequires: ASSISTANT_MAIL_API_KEY (secret)
AgentiSend As a remote MCP server
claude mcp add --transport http agentisend https://api.agentisend.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: AGENTISEND_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only AgentiSend 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 Assistant Mail MCP asks for
ASSISTANT_MAIL_API_BASE_URLASSISTANT_MAIL_API_KEY (secret)
Only AgentiSend asks for
AGENTISEND_API_KEY (secret)AGENTISEND_MCP_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Assistant Mail MCP · What it can do: AgentiSend · 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.