Ext Ops Panel
Open dashboard
Comparison

mcpd vs Google Search Console

mcpd is a plugin bundle for AI coding tools published by yn01. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Google Search Console is an MCP server published by acamolese. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-26. 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

Where each is published
MarketplacemcpdGoogle Search Console
Claude Code: claude-plugins-community Listed
Version: b99b1bb
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.0.1
Downloads/month (PyPI): 986
Downloads/week (PyPI): 674
Forks (GitHub): 4
Stars (GitHub): 9
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 3.0.1
Downloads/month (PyPI): 986
Downloads/week (PyPI): 674
Forks (GitHub): 4
Stars (GitHub): 9
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

mcpd vs Google Search Console
FactmcpdGoogle Search Console
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)9 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-google-search-console)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published6, secrets among them: 2
Licence (differs)Not statedMIT
Repository (differs)github.com/yn01/claude-pluginsgithub.com/acamolese/google-search-console-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

mcpd

In its own words, on Claude Code: claude-plugins-community:

Diagnose MCP server configuration, connectivity, and available tools — all in one command. mcpd reads your global and project-level MCP config files, checks that required environment variables are set, verifies server connectivity (stdio and SSE/HTTP), and lists all available tools. Get a clear picture of your entire MCP setup in seconds.

Google Search Console

In its own words, on Official MCP Registry:

Google Search Console: SEO audits, performance queries, URL inspection, indexing checks.

How to run each

mcpd As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mcpd@claude-community

Google Search Console As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GSC_CLIENT_SECRET=<YOUR_GSC_CLIENT_SECRET>" --env "GSC_REFRESH_TOKEN=<YOUR_GSC_REFRESH_TOKEN>" --transport stdio google-search-console-mcp -- uvx mcp-google-search-console

Requires: GSC_CLIENT_SECRET (secret), GSC_REFRESH_TOKEN (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 mcpd publish no settings it asks for, so we do not compare settings.

What it can do: mcpd · What it can do: Google Search Console · 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. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. 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