gws vs LMCP
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. LMCP is an MCP server published by local-mcp.com. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-29. 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 | ||
|---|---|---|
| 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: 3.0.429 Downloads/month (npm): 10 964 Downloads/week (npm): 1 023 Forks (GitHub): 11 Stars (GitHub): 74 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 3.0.429 Downloads/month (npm): 10 964 Downloads/week (npm): 1 023 Forks (GitHub): 11 Stars (GitHub): 74 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 · | LMCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 4 |
| Stars (GitHub) (differs) | 5 | 74 |
| Forks (GitHub) (differs) | 4 | 11 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 29 | 16 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cblecker/claude-plugins | github.com/colibird-ai/local-mcp-releases |
| Changes in the last 7 days (differs) | 0 | 12 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-28 |
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…
-
Use this skill whenever the user wants to operate Google Workspace from the command line with gog/gogcli, including Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Apps…
-
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…
-
Google Workspace integration (Gmail, Drive, Calendar)
-
gog-hardened
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
What each says it does
gws
Google Workspace CLI skills for Gmail, Calendar, Drive, Docs, Sheets, Slides, Meet, and Tasks
LMCP
Mac & Windows: let ChatGPT, Claude & Cursor use your email, calendar, iMessage, Teams, files.
How to run each
gws
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
LMCP As a remote MCP server
claude mcp add --transport http local-mcp https://local-mcp.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LMCP 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 gws publish no settings it asks for, so we do not compare settings.
What it can do: gws · What it can do: LMCP · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.