Multi-Account Gmail vs Gmail
Multi-Account Gmail is an MCP server published by cunicopia-dev. Marketplaces we read that list it: 1 (Official MCP Registry). Gmail is an MCP server published by mcp-z. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  Multi-Account Gmail | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Downloads/month (PyPI): 211 Downloads/week (PyPI): 53 Forks (GitHub): 4 Stars (GitHub): 5 Not marked · First seen |
Listed Version: 2.3.3 Downloads/month (npm): 5 527 Downloads/week (npm): 2 390 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 | Multi-Account Gmail | Gmail |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | On your machine (multi-account-gmail-mcp) | On your machine (@mcp-z/mcp-gmail) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 13, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cunicopia-dev/gmail-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| 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
Multi-Account Gmail
Multi-account Gmail MCP server — read, search, draft, and label across every inbox.
Gmail
Gmail integration with OAuth authentication, message search, batch operations, and Sheets export
How to run each
Multi-Account Gmail As a local MCP server: PyPI package
claude mcp add --transport stdio multi-account-gmail-mcp -- uvx multi-account-gmail-mcpGmail As a local MCP server: npm package
claude mcp add --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --transport stdio mcp-gmail -- npx -y @mcp-z/mcp-gmailRequires: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Multi-Account Gmail asks for
GMAIL_MCP_CLIENT_SECRETGMAIL_MCP_DBGMAIL_MCP_OAUTH_PORT
Only Gmail asks for
AUTH_MODEBASE_URLDCR_MODEDCR_STORE_URIDCR_VERIFY_URLGOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET (secret)GOOGLE_SERVICE_ACCOUNT_KEY_FILEHEADLESSLOG_LEVELPORTREDIRECT_URI
Show the remaining 1
RESOURCE_STORE_URI
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Multi-Account Gmail · What it can do: Gmail · Compare two other plugins
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.