Ext Ops Panel
Open dashboard
Comparison

gws vs Grounders MCP

gws is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

gws is a plugin bundle for AI coding tools published by orieg. No marketplace we read lists it any more. Grounders MCP is an MCP server published by ItsBreeze. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacegwsGrounders MCP
Community marketplace orieg/gws-connector Removed on 2026-10-15
Version: 0.4.3
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

gws vs Grounders MCP
Factgwsno longer listed · Grounders MCP
Marketplaces that list it (differs)01
Stars (GitHub) (differs)10
Forks (GitHub) (differs)20
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.grounders.app/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/orieg/gws-connectorgithub.com/itsbreeze/google-multi-account-mcp
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-23

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of gws

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • gws-connector io.github.orieg/gws-connector

    Multi-account Google Workspace MCP — Gmail, Calendar, Drive, Sheets, Docs with smart routing.

    by orieg · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community · Describes nearly the same job

  • mcp-google-workspace

    Google Workspace integration (Gmail, Drive, Calendar)

    by henkisdabro · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Google Workspace

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

    by aaronsb · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Hub

    Multiple Google accounts (Gmail, Calendar, Drive, Contacts, Tasks) in one Claude connector.

    by ItsBreeze · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Google Workspace

    Google Workspace MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and more

    by mindstone · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token

    Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token-efficient, macOS…

    by adelaidasofia · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

gws

In its own words, on Community GitHub marketplaces:

Multi-account workspace integration — Mail, Calendar, Drive, Sheets, and Docs with smart account routing for Gmail and Google Workspace

Grounders MCP

In its own words, on Official MCP Registry:

Multiple Google accounts (Gmail, Calendar, Drive, Contacts, Tasks) in one Claude connector.

How to run each

gws

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Grounders MCP As a remote MCP server

Claude Code
claude mcp add --transport http grounders-mcp https://mcp.grounders.app/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Grounders MCP has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Grounders MCP publish no settings it asks for, so we do not compare settings.

What it can do: gws · What it can do: Grounders MCP · 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. 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