MCP Google Search Console vs Google Webtools MCP
MCP Google Search Console is an MCP server published by crunchtools. Marketplaces we read that list it: 1 (Official MCP Registry). Google Webtools MCP is an MCP server published by stufently. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
| Marketplace |  MCP Google Search Console |  Google Webtools MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (PyPI): 72 Downloads/week (PyPI): 67 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.2.2 Forks (GitHub): 0 Stars (GitHub): 6 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 | MCP Google Search Console | Google Webtools MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 6 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp-google-search-console-crunchtools) | On your machine (ghcr.io/stufently/google-webtools-mcp:1.2.2) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/crunchtools/mcp-google-search-console | github.com/stufently/google-webtools-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
MCP Google Search Console
Secure MCP server for Google Search Console analytics, sitemaps, and URL inspection
Google Webtools MCP
Google Search Console + GA4 for AI agents: properties, reports, indexing, verification, SEO.
How to run each
MCP Google Search Console As a local MCP server: PyPI package
claude mcp add --transport stdio google-search-console -- uvx mcp-google-search-console-crunchtoolsGoogle Webtools MCP As a local MCP server: Docker image
claude mcp add --env "GOOGLE_SERVICE_ACCOUNT_KEY=<YOUR_GOOGLE_SERVICE_ACCOUNT_KEY>" --transport stdio google-webtools-mcp -- docker run -i --rm -e GOOGLE_SERVICE_ACCOUNT_KEY ghcr.io/stufently/google-webtools-mcp:1.2.2Requires: GOOGLE_SERVICE_ACCOUNT_KEY (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
The marketplaces of MCP Google Search Console publish no settings it asks for, so we do not compare settings.
What it can do: MCP Google Search Console · What it can do: Google Webtools MCP · Compare two other plugins
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.