Labsco
MCP SERVER

Google Search Console MCP

by samalyxx

Query a Search Console property for the analyses people normally rebuild by hand — queries stuck at positions 4-15, pages decaying across several periods, two URLs splitting one query — and check a number before it goes into a client deck.

SEO, Web & Product AnalyticsVerified
Summary
The analysis layer that usually lives in a spreadsheet is on the server side of the call.

Most Search Console clients hand back rows and leave the interpretation to you; here traffic_drop_diagnosis attributes a loss to ranking, CTR or demand, ctr_opportunities compares against an expected-CTR curve, and search_intent_breakdown sorts queries into informational, commercial, transactional, navigational and local buckets. verify_claim is the unusual one: it re-queries the property to test a number you are about to present, against a tolerance percent you set. delete_site and delete_sitemap are both marked destructive in their own descriptions, and the URL Inspection and Indexing calls run sequentially, so batches are quota-bound by design.

What it is

A Search Console front end with 40 tools, covering the Search Analytics, URL Inspection, Sitemaps and Indexing APIs for the properties one authenticated account or service account can reach.

What you get
  • Raw pulls when you know what you want: search_analytics for custom dimensions and filters, advanced_filter_query for up to 50,000 rows, top_queries and top_pages with cross-filtering, and dimension_breakdown for a single dimension.
  • Period framing done for you: performance_overview returns a snapshot against the previous period with daily trend, devices and search appearances, compare_periods sets current against previous by page, query, country, device or appearance.
  • Diagnoses rather than tables: traffic_drop_diagnosis separates ranking loss from CTR loss, demand decline or a mixed signal; content_decay looks across several equal periods instead of one noisy comparison; anomaly_alerts watches the latest period against the one before it.
  • Opportunity finders with thresholds you set: quick_wins for positions 4-15, ctr_opportunities against an expected-CTR curve, cannibalization_check, device_country_opportunities, long_tail_questions and internal_link_opportunities.
  • Content briefs backed by the property's own data: page_query_matrix maps pages to the queries driving them, query_page_fit reads one URL's query mix and intent, title_meta_brief builds a refresh brief from high-impression low-CTR queries.
  • Index-side work: inspect_url, batch_inspect_urls and index_coverage_summary; list_sitemaps, get_sitemap, submit_sitemap and delete_sitemap; indexing_publish_url, indexing_batch_publish and indexing_get_metadata.
  • Reporting and self-checks: multi_site_dashboard compares configured properties, generate_markdown_report writes a report to GSC_REPORT_DIR, and verify_claim re-queries the API to test a numeric claim against a tolerance you give it.
Requirements

A Search Console property and an account or service account with access to it, plus GSC_AUTH_MODE, GSC_KEY_FILE and GSC_SITE_URL in the environment. add_site, submit_sitemap and delete_sitemap need write scope, and generate_markdown_report writes into GSC_REPORT_DIR.

Setup effort

One command plus a key — npx -y gsc-seo-mcp, then supply credentials