Ext Ops Panel
Open dashboard
Comparison

Google Workspace vs Fluxmail

Google Workspace is an MCP server published by aaronsb. Marketplaces we read that list it: 1 (Official MCP Registry). Fluxmail is an MCP server published by churichard. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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
MarketplaceGoogle WorkspaceFluxmail
Official MCP Registry Listed
Version: 4.8.0
Downloads/month (npm): 5 596
Downloads/week (npm): 920
Forks (GitHub): 56
Stars (GitHub): 192
Not marked · First seen
Listed
Version: 0.12.0
Downloads/month (npm): 2 436
Downloads/week (npm): 557
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.15.0
Downloads/month (npm): 2 436
Downloads/week (npm): 557
Forks (GitHub): 0
Stars (GitHub): 7
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

Google Workspace vs Fluxmail
FactGoogle WorkspaceFluxmail
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)192 (better)7 (worse)
Forks (GitHub) (differs)56 (better)0 (worse)
Last release (differs)2026-10-16 (worse)2026-10-17 (better)
Where it runs (differs)On your machine (@aaronsb/google-workspace-mcp)On your machine (fluxmail)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 04, secrets among them: 2
Licence (differs)Not statedElastic-2.0
Repository (differs)github.com/aaronsb/google-workspace-mcpgithub.com/churichard/fluxmail
Changes in the last 7 days (differs)24
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

Google Workspace

In its own words, on Official MCP Registry:

Give AI agents access to Gmail, Calendar, Drive, and more — multi-account, manifest-driven

Fluxmail

In its own words, on Official MCP Registry:

Read, search, draft, send, and organize email through Gmail, Outlook, and IMAP/SMTP mailboxes.

How to run each

Google Workspace As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio google-workspace -- npx -y @aaronsb/google-workspace-mcp

Fluxmail As a local MCP server: npm package

Claude Code
claude mcp add --env "FLUXMAIL_LICENSE_KEY=<YOUR_FLUXMAIL_LICENSE_KEY>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --transport stdio fluxmail -- npx -y fluxmail stdio

Requires: FLUXMAIL_LICENSE_KEY (secret), 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 Google Workspace asks for

None

Only Fluxmail asks for

  • FLUXMAIL_DATA_DIR
  • FLUXMAIL_LICENSE_KEY (secret)

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

What it can do: Google Workspace · What it can do: Fluxmail · Compare two other plugins

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.

Where the data comes from: how the catalog is built