Ext Ops Panel
Open dashboard
Comparison

Gmail vs Assistant Mail MCP

Gmail is an MCP server published by Sallytion. Marketplaces we read that list it: 1 (Docker MCP Catalog). Assistant Mail MCP is an MCP server published by AssistantMail. 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
MarketplaceGmailAssistant Mail MCP
Docker MCP Catalog Listed
Version: sha256:9d806c6ba375
Forks (GitHub): 9
Stars (GitHub): 12
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.1
Downloads/month (npm): 266
Downloads/week (npm): 38
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

Gmail vs Assistant Mail MCP
FactGmailAssistant Mail MCP
Marketplaces that list it11
Stars (GitHub) (differs)12 (better)0 (worse)
Forks (GitHub) (differs)9 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (yashtekwani/gmail-mcp)On your machine (@assistantmail/assistantmail-mcp)
Transportstdiostdio
Tools it declares (differs)3Not published
Environment variables it asks for (differs)6, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/sallytion/gmail-mcpgithub.com/assistantmail/assistantmail-mcp
Changes in the last 7 days00
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

Gmail

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for Gmail operations using IMAP/SMTP with app password authentication. Supports listing messages, searching emails, and sending messages. To create your app password, visit your Google Account settings under Security > App Passwords. Or visit the link https://myaccount.google.com/apppasswords.

Assistant Mail MCP

In its own words, on Official MCP Registry:

Agent email with allowlist and consent via AssistantMail.

How to run each

Gmail As a local MCP server: Docker image

Claude Code
claude mcp add --env "EMAIL_PASSWORD=<YOUR_EMAIL_PASSWORD>" --transport stdio gmail-mcp -- docker run -i --rm -e EMAIL_PASSWORD yashtekwani/gmail-mcp

Requires: EMAIL_PASSWORD (secret)

Assistant Mail MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "ASSISTANT_MAIL_API_KEY=<YOUR_ASSISTANT_MAIL_API_KEY>" --transport stdio assistantmail-mcp -- npx -y @assistantmail/assistantmail-mcp

Requires: ASSISTANT_MAIL_API_KEY (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 Assistant Mail MCP publish no list of tools, so we do not compare tools.

Settings each asks for

Only Gmail asks for

  • EMAIL_ADDRESS
  • EMAIL_PASSWORD (secret)
  • IMAP_HOST
  • IMAP_PORT
  • SMTP_HOST
  • SMTP_PORT

Only Assistant Mail MCP asks for

  • ASSISTANT_MAIL_API_BASE_URL
  • ASSISTANT_MAIL_API_KEY (secret)

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

What it can do: Gmail · What it can do: Assistant Mail 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