gsc-pap vs Google Webtools MCP
gsc-pap is a plugin bundle for AI coding tools published by aliarifsoydas. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, 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-11-05. 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 |  gsc-pap |  Google Webtools MCP |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 0.3.4 Forks (GitHub): 0 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 | gsc-pap | Google Webtools MCP |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 (worse) | 6 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-03 (better) | 2026-10-14 (worse) |
| Where it runs (differs) | Remote server (mcp.gscpap.com/mcp) | On your machine (ghcr.io/stufently/google-webtools-mcp:1.2.2) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aliarifsoydas/gsc-pap-claude-plugin | github.com/stufently/google-webtools-mcp |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 4 days ago returned HTTP 405 | no remote endpoint we check |
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
gsc-pap
Ask Claude about your Google Search Console top queries, decaying pages, ranking trends, content cannibalization, quick wins. Plug-and-play hosted MCP bridge: sign in with Google, copy a token, paste it. No GCP project, no Python, no JSON config files to manage. 18 read-only tools covering Search Analytics, URL Inspection, Sitemaps, and a built-in archive for trending data beyond Google's 16-month window. Per-site authorization layer means you decide which properties Claude can see, even though OAuth grants account-wide access. All tool calls audited at app.gscpap.com Built for SEO consultants, in-house marketers, and developers who want to delegate analysis to AI without exposing their Google credentials or wrangling 1000-line CSV exports.
Google Webtools MCP
Google Search Console + GA4 for AI agents: properties, reports, indexing, verification, SEO.
How to run each
gsc-pap As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gsc-pap@claude-communityGoogle 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.
Only gsc-pap 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 gsc-pap publish no settings it asks for, so we do not compare settings.
What it can do: gsc-pap · What it can do: Google Webtools MCP · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.