Gmail vs pylos-mcp
Gmail is an MCP server published by Sallytion. 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: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-23. 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 |  Gmail |   pylos-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.0 Downloads/month (npm): 1 739 Downloads/week (npm): 358 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.3.0 Downloads/month (npm): 1 739 Downloads/week (npm): 358 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
| Fact | Gmail | pylos-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 12 (better) | 4 (worse) |
| Forks (GitHub) (differs) | 9 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (yashtekwani/gmail-mcp) | On your machine (pylos-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | 8, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/sallytion/gmail-mcp | github.com/adamvass/pylos-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| 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
Gmail
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.
pylos-mcp
Email MCP server for Gmail, Outlook and any IMAP mailbox, hardened against prompt injection
How to run each
Gmail As a local MCP server: Docker image
claude mcp add --env "EMAIL_PASSWORD=<YOUR_EMAIL_PASSWORD>" --transport stdio gmail-mcp -- docker run -i --rm -e EMAIL_PASSWORD yashtekwani/gmail-mcpRequires: EMAIL_PASSWORD (secret)
pylos-mcp As a local MCP server: npm package
claude mcp add --env "EMAIL_PASSWORD=<YOUR_EMAIL_PASSWORD>" --env "EMAIL_USER=<YOUR_EMAIL_USER>" --transport stdio pylos-mcp -- npx -y pylos-mcpRequires: 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 Gmail asks for
EMAIL_ADDRESSIMAP_PORTSMTP_HOSTSMTP_PORT
Only pylos-mcp asks for
ACCOUNTSCAPABILITIESEMAIL_USERMS_CLIENT_IDMS_TENANTPROVIDER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Gmail · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.