Ext Ops Panel
Open dashboard
Comparison

google-workspace-mcp vs Gmail

google-workspace-mcp is a plugin bundle for AI coding tools published by taylorwilsdon. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Gmail is an MCP server published by mcp-z. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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-workspace-mcpGmail
Community marketplace taylorwilsdon/google_workspace_mcp Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.3.3
Downloads/month (npm): 613
Downloads/week (npm): 2 390
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.3.3
Downloads/month (npm): 613
Downloads/week (npm): 2 390
Forks (GitHub): 2
Stars (GitHub): 5
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-mcp vs Gmail
Factgoogle-workspace-mcpGmail
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub5
Forks (GitHub) (differs)No figure on GitHub2
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleOn your machine (@mcp-z/mcp-gmail)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 313, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/taylorwilsdon/google_workspace_mcpgithub.com/mcp-z/mcp-gmail
Changes in the last 7 days (differs)20
First seen (differs)2026-11-082026-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-mcp

In its own words, on Community GitHub marketplaces:

Complete Google Workspace integration -- Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, and Custom Search via MCP with workflow guidance.

Gmail

In its own words, on Official MCP Registry:

Gmail integration with OAuth authentication, message search, batch operations, and Sheets export

How to run each

google-workspace-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add taylorwilsdon/google_workspace_mcp
/plugin install google-workspace-mcp@google-workspace-mcp

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>" --transport stdio mcp-gmail -- npx -y @mcp-z/mcp-gmail

Requires: 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 google-workspace-mcp asks for

  • GOOGLE_OAUTH_CLIENT_ID (secret)
  • GOOGLE_OAUTH_CLIENT_SECRET (secret)
  • OAUTHLIB_INSECURE_TRANSPORT (secret)
  • WORKSPACE_MCP_HTTP_PORT
  • WORKSPACE_MCP_PERMISSIONS
  • WORKSPACE_MCP_READ_ONLY
  • WORKSPACE_MCP_TOOLS
  • WORKSPACE_MCP_TOOL_TIER

Only Gmail asks for

  • AUTH_MODE
  • BASE_URL
  • DCR_MODE
  • DCR_STORE_URI
  • DCR_VERIFY_URL
  • GOOGLE_CLIENT_ID
  • GOOGLE_CLIENT_SECRET (secret)
  • GOOGLE_SERVICE_ACCOUNT_KEY_FILE
  • HEADLESS
  • LOG_LEVEL
  • PORT
  • REDIRECT_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: google-workspace-mcp · What it can do: Gmail · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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