MCP server for Google Search Console. Query search analytics, inspect URLs, and monitor SEO performance from any MCP-compatible client.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"gsc-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# gsc-mcp **Google Search Console as MCP tools** — query search analytics, inspect URLs, and monitor SEO performance from any MCP-compatible AI client (Claude Desktop, Claude Code, Claude.ai, Gemini CLI, Cursor, etc.). Zero vendor middleware. Zero ongoing cost. Each user authenticates with their own Google account against Google's free Search Console API. --- ## Why this exists Pulling GSC data into an AI client normally means either (a) manual CSV exports, (b) a paid data-pipeline vendor like Windsor or Coupler, or (c) building your own script and glue. This is option (d): a small, self-contained MCP server you install once and use from anywhere. Pairs naturally with [Google's Analytics MCP](https://github.com/googleanalytics/google-analytics-mcp) for a complete SEO + user behavior picture. --- ## Tools All tools are read-only. No writes in v1. | Tool | What it does | | --- | --- | | `gsc_list_sites` | Enumerate every verified Search Console property for the authenticated user | | `gsc_query_search_analytics` | Flexible analytics query — any combination of dimensions (query, page, country, device, date, searchAppearance) and filters | | `gsc_top_queries` | Convenience: top N search queries for a site over a recent window | | `gsc_top_pages` | Convenience: top N landing pages for a site over a recent window | | `gsc_inspect_url` | URL inspection — indexing verdict, coverage state, Google-chosen canonical, last crawl, mobile usability, rich results | | `gsc_list_sitemaps` | List registered sitemaps with status, errors, warnings, last submitted date | | `gsc_health_check` | Auth + API reachability diagnostic (use this first when something breaks) | --- ## Setup Three steps. ~15 minutes total. ### 1. Google Cloud — create an OAuth client 1. Open [Google Cloud Console](https://console.cloud.google.com/). 2. Create (or reuse) a project. Name it something like `gsc-mcp`. 3. Enable the Search Console API: [one-click link](https://console.cloud.google.com/api…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.