Ext Ops Panel
Open dashboard
Comparison

Gmail vs io.github.markswendsen-code/gmail

Gmail is an MCP server published by domdomegg. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.markswendsen-code/gmail is an MCP server published by markswendsen-code. 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

Where each is published
MarketplaceGmailio.github.markswendsen-code/gmail
Official MCP Registry Listed
Version: 2.4.0
Downloads/month (npm): 2 991
Downloads/week (npm): 181
Forks (GitHub): 9
Stars (GitHub): 11
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 119
Downloads/week (npm): 24
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 io.github.markswendsen-code/gmail
FactGmailio.github.markswendsen-code/gmail
Marketplaces that list it11
Stars (GitHub) (differs)11 (better)0 (worse)
Forks (GitHub) (differs)9 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (gmail-mcp)On your machine (@striderlabs/mcp-gmail)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 23, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/domdomegg/gmail-mcpgithub.com/markswendsen-code/mcp-gmail
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 Official MCP Registry:

Allow AI systems to read, send, archive, and manage emails via Gmail.

io.github.markswendsen-code/gmail

In its own words, on Official MCP Registry:

Gmail MCP server — send, read, and search email. By Strider Labs.

How to run each

Gmail As a local MCP server: npm package

Claude Code
claude mcp add --env "GOOGLE_ACCESS_TOKEN=<YOUR_GOOGLE_ACCESS_TOKEN>" --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "MCP_TRANSPORT=<YOUR_MCP_TRANSPORT>" --transport stdio gmail-mcp -- npx -y gmail-mcp

Requires: GOOGLE_ACCESS_TOKEN (secret), GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), MCP_TRANSPORT

io.github.markswendsen-code/gmail As a local MCP server: npm package

Claude Code
claude mcp add --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GOOGLE_REFRESH_TOKEN=<YOUR_GOOGLE_REFRESH_TOKEN>" --transport stdio gmail -- npx -y @striderlabs/mcp-gmail

Requires: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), GOOGLE_REFRESH_TOKEN (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 Gmail asks for

  • GOOGLE_ACCESS_TOKEN (secret)
  • MCP_TRANSPORT

Only io.github.markswendsen-code/gmail asks for

  • GOOGLE_REFRESH_TOKEN (secret)

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

What it can do: Gmail · What it can do: io.github.markswendsen-code/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.

Where the data comes from: how the catalog is built