Ext Ops Panel
Open dashboard
Comparison

Resend vs pylos-mcp

Resend is an MCP server published by resend. Marketplaces we read that list it: 1 (Docker MCP Catalog). pylos-mcp is an MCP server published by adamVass. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceResendpylos-mcp
Docker MCP Catalog Listed
Version: sha256:2a786579214e
Forks (GitHub): 90
Pulls (Docker Hub): 21 941
Stars (Docker Hub): 5
Stars (GitHub): 576
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.0
Downloads/month (npm): 1 433
Downloads/week (npm): 1 245
Forks (GitHub): 0
Stars (GitHub): 4
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

Resend vs pylos-mcp
FactResendpylos-mcp
Marketplaces that list it11
Stars (GitHub) (differs)576 (better)4 (worse)
Pulls (Docker Hub) (differs)21 941No figure on Docker Hub
Forks (GitHub) (differs)90 (better)0 (worse)
Last release (differs)Not published2026-10-19
Where it runs (differs)On your machine (mcp/resend)On your machine (pylos-mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)3, secrets among them: 18, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/resend/mcp-send-emailgithub.com/adamvass/pylos-mcp
Changes in the last 7 days (differs)04
First seen2026-10-112026-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.

pylos-mcp

In its own words, on Official MCP Registry:

Email MCP server for Gmail, Outlook and any IMAP mailbox, hardened against prompt injection

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)

pylos-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "EMAIL_PASSWORD=<YOUR_EMAIL_PASSWORD>" --env "EMAIL_USER=<YOUR_EMAIL_USER>" --transport stdio pylos-mcp -- npx -y pylos-mcp

Requires: EMAIL_PASSWORD (secret), EMAIL_USER

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

Tools each declares

The marketplaces of pylos-mcp 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 pylos-mcp asks for

  • ACCOUNTS
  • CAPABILITIES
  • EMAIL_PASSWORD (secret)
  • EMAIL_USER
  • IMAP_HOST
  • MS_CLIENT_ID
  • MS_TENANT
  • PROVIDER

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

What it can do: Resend · What it can do: pylos-mcp · 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 . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built