Comparison

Resend vs SuprSend

Resend is an MCP server published by resend. Marketplaces we read that list it: 1 (Docker MCP Catalog). SuprSend is an MCP server published by suprsend. 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

Where each is published
Marketplace	Resend	SuprSend
Docker MCP Catalog	Listed Version: sha256:2a786579214e Forks (GitHub): 91 Pulls (Docker Hub): 21 822 Stars (Docker Hub): 5 Stars (GitHub): 576 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed, marked deprecated Version: 1.0.1 Downloads/month (npm): 495 Downloads/week (npm): 76 Forks (GitHub): 2 Stars (GitHub): 12 Not marked · First seen 2026-10-11

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

Resend vs SuprSend
Fact	Resend	SuprSend
Marketplaces that list it	1	1
Stars (GitHub) (differs)	576 (better)	12 (worse)
Pulls (Docker Hub) (differs)	21 822	No figure on Docker Hub
Forks (GitHub) (differs)	91 (better)	2 (worse)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/resend)	On your machine (suprsend)
Transport	stdio	stdio
Tools it declares (differs)	1	Not published
Environment variables it asks for	3, secrets among them: 1	3, secrets among them: 1
Licence (differs)	MIT	Not stated
Repository (differs)	github.com/resend/mcp-send-email	github.com/suprsend/cli
Changes in the last 7 days (differs)	0	1
First seen	2026-10-11	2026-10-11

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

Resend

In its own words, on Docker MCP Catalog:

The official MCP server to send emails and interact with Resend.

SuprSend

In its own words, on Official MCP Registry:

Manage SuprSend entities — workflows, templates, users, objects, tenants — from your AI assistant.

How to run each

Resend As a local MCP server: Docker image

Claude Code

claude mcp add --env "RESEND_API_KEY=<YOUR_RESEND_API_KEY>" --transport stdio resend -- docker run -i --rm -e RESEND_API_KEY mcp/resend

Requires: RESEND_API_KEY (secret)

SuprSend As a local MCP server: npm package

Claude Code

claude mcp add --env "SUPRSEND_SERVICE_TOKEN=<YOUR_SUPRSEND_SERVICE_TOKEN>" --transport stdio cli -- npx -y suprsend start-mcp-server --workflows all

Requires: SUPRSEND_SERVICE_TOKEN (secret)

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

Tools each declares

The marketplaces of SuprSend publish no list of tools, so we do not compare tools.

Settings each asks for

Only Resend asks for

REPLY_TO_EMAIL_ADDRESSES
RESEND_API_KEY (secret)
SENDER_EMAIL_ADDRESS

Only SuprSend asks for

SUPRSEND_BASE_URL
SUPRSEND_MGMNT_URL
SUPRSEND_SERVICE_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Resend · What it can do: SuprSend · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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 2026-10-13. We publish no contact details for plugin publishers.