Ext Ops Panel
Open dashboard
Comparison

Sendsets vs Email (IMAP/SMTP)

Sendsets is an MCP server published by AddisonHoff. Marketplaces we read that list it: 1 (Official MCP Registry). Email (IMAP/SMTP) is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceSendsetsEmail (IMAP/SMTP)
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.3.2
Downloads/month (npm): 477
Downloads/week (npm): 118
Forks (GitHub): 4
Stars (GitHub): 13
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

Sendsets vs Email (IMAP/SMTP)
FactSendsetsEmail (IMAP/SMTP)
Marketplaces that list it11
Stars (GitHub) (differs)3 (worse)13 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.sendsetsapi.com/v1/mcp)On your machine (@mindstone/mcp-server-email-imap)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/addisonhoff/sendsetsgithub.com/mindstone/mcp-servers
Changes in the last 7 days (differs)80
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days ago, requires a keyno remote endpoint we check

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

Sendsets

In its own words, on Official MCP Registry:

Cold email API for AI agents: connect mailboxes, warm up, run campaigns and handle replies.

Email (IMAP/SMTP)

In its own words, on Official MCP Registry:

Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers

How to run each

Sendsets As a remote MCP server

Claude Code
claude mcp add --transport http sendsets https://api.sendsetsapi.com/v1/mcp

Email (IMAP/SMTP) As a local MCP server: npm package

Claude Code
claude mcp add --env "EMAIL_IMAP_EMAIL=<YOUR_EMAIL_IMAP_EMAIL>" --env "EMAIL_IMAP_PASSWORD=<YOUR_EMAIL_IMAP_PASSWORD>" --transport stdio mcp-server-email-imap -- npx -y @mindstone/mcp-server-email-imap

Requires: EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD (secret)

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

Only Sendsets 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 Sendsets publish no settings it asks for, so we do not compare settings.

What it can do: Sendsets · What it can do: Email (IMAP/SMTP) · 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.

Where the data comes from: how the catalog is built