Ext Ops Panel
Open dashboard
Comparison

io.github.csitte/mailwarden vs io.github.markswendsen-code/gmail

io.github.csitte/mailwarden is an MCP server published by csitte. 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-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
Marketplaceio.github.csitte/mailwardenio.github.markswendsen-code/gmail
Official MCP Registry Listed
Version: 0.22.1
Downloads/month (npm): 1 133
Downloads/week (npm): 307
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.csitte/mailwarden vs io.github.markswendsen-code/gmail
Factio.github.csitte/mailwardenio.github.markswendsen-code/gmail
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-12Not published
Where it runs (differs)On your machine (mailwarden)On your machine (@striderlabs/mcp-gmail)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 03, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/csitte/mailwardengithub.com/markswendsen-code/mcp-gmail
Changes in the last 7 days (differs)10
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

io.github.csitte/mailwarden

In its own words, on Official MCP Registry:

Gmail MCP server for email triage: search, labels, archive, trash, unsubscribe, snooze.

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

io.github.csitte/mailwarden As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mailwarden -- npx -y mailwarden

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 io.github.csitte/mailwarden asks for

  • MAILWARDEN_AUTO_SWEEP
  • MAILWARDEN_CREDENTIALS
  • MAILWARDEN_DIR
  • MAILWARDEN_DOWNLOAD_DIR

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

  • GOOGLE_CLIENT_ID
  • GOOGLE_CLIENT_SECRET (secret)
  • GOOGLE_REFRESH_TOKEN (secret)

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

What it can do: io.github.csitte/mailwarden · 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