gws vs Google Workspace
gws is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
gws is a plugin bundle for AI coding tools published by cblecker. No marketplace we read lists it any more. Google Workspace is an MCP server published by aaronsb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
| Marketplace |  Google Workspace | |
|---|---|---|
| Community marketplace cblecker/claude-plugins | Removed on 2026-10-20 Version: 2.1.1 Forks (GitHub): 4 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.8.0 Downloads/month (npm): 5 596 Downloads/week (npm): 920 Forks (GitHub): 56 Stars (GitHub): 192 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
| Fact | gwsno longer listed · | Google Workspace |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | 192 |
| Forks (GitHub) (differs) | 4 | 56 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@aaronsb/google-workspace-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 29 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cblecker/claude-plugins | github.com/aaronsb/google-workspace-mcp |
| Changes in the last 7 days (differs) | 4 | 1 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
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.
-
Google Workspace administration via the gws CLI. Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. 5 Python tools, 3 reference guides, 43…
-
Drive Google Workspace from the terminal with the `gog` CLI (gogcli). Use when sending/searching Gmail, managing Calendar events, uploading to Drive, editing Docs/Sheets/Slides…
-
Google Workspace MCP server (Gmail, Drive, Docs, Sheets, Slides, Calendar, Forms, Chat, Photos, Contacts) plus skills for the card/email DSL, code mode, and Qdrant search over…
-
gog-hardened
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
-
Google Workspace MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and more
-
Gmail, Calendar, Drive, Sheets, Tasks and Contacts for agents, with your own Google login
What each says it does
gws
Google Workspace CLI skills for Gmail, Calendar, Drive, Docs, Sheets, Slides, Meet, and Tasks
Google Workspace
Give AI agents access to Gmail, Calendar, Drive, and more — multi-account, manifest-driven
How to run each
gws
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Google Workspace As a local MCP server: npm package
claude mcp add --transport stdio google-workspace -- npx -y @aaronsb/google-workspace-mcpCommands 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
The marketplaces of gws publish no settings it asks for, so we do not compare settings.
What it can do: gws · What it can do: Google Workspace · 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.