Gmail vs mailsocket
Gmail is an MCP server published by Sallytion. Marketplaces we read that list it: 1 (Docker MCP Catalog). mailsocket is an MCP server published by mailsocket.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  mailsocket |
|---|---|---|
| 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: 0.4.1 Downloads/month (PyPI): 861 Downloads/week (PyPI): 164 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
| Fact | Gmail | mailsocket |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 9 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (yashtekwani/gmail-mcp) | Remote server (mcp.mailsocket.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/sallytion/gmail-mcp | github.com/mailsocket/mailsocket-sdk |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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.
mailsocket
Email inboxes for AI agents: create an inbox, then block until the OTP or magic link arrives.
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)
mailsocket As a remote MCP server
claude mcp add --transport http mailsocket-mcp https://mcp.mailsocket.app/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: MAILSOCKET_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of mailsocket publish no list of tools, so we do not compare tools.
Settings each asks for
Only Gmail asks for
EMAIL_ADDRESSEMAIL_PASSWORD (secret)IMAP_HOSTIMAP_PORTSMTP_HOSTSMTP_PORT
Only mailsocket asks for
MAILSOCKET_API_KEY (secret)MAILSOCKET_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Gmail · What it can do: mailsocket · 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.