Google Search Console
Query Search Console performance, sitemaps, and URL inspection from your agent while shipping and tuning discoverability.
Overview
com.mcparmory/google-search-console is a MCP server for the Launch phase that queries Google Search Console analytics, sitemaps, and URL inspection from your agent.
What is this MCP server?
- Query search analytics and performance data for properties you control
- Manage sitemaps and inspect individual URLs and indexing status
- Stdio MCP 1.0.3 via uvx (mcparmory-google-search-console) or Docker OCI image
- Official GSC API workflow exposed as agent tools—not a scraper
- Repository sourced from github.com/mcparmory/registry
- Server version 1.0.3 on MCP schema 2025-12-11
- PyPI package mcparmory-google-search-console and OCI ghcr.io/mcparmory/google-search-console:1.0.3
- Stdio transport on both package entries
Community signal: 25 GitHub stars.
What problem does it solve?
After you ship, you need GSC metrics and index status in the same workflow where you fix pages—but the Search Console UI pulls you out of the agent.
Who is it for?
Solo founders maintaining their own site or docs who already use Search Console and want MCP-driven SEO checks after launch.
Skip if: Builders without a verified GSC property, or anyone who only needs public SERP snapshots without authenticated site data.
What do I get? / Deliverables
Your agent can answer performance and indexing questions and trigger sitemap or inspection actions using authenticated GSC tools.
- Search analytics and performance summaries usable in agent-driven SEO reports
- Sitemap operations and per-URL inspection results tied to fix tasks in your repo
Recommended MCP Servers
Journey fit
Search Console is the canonical Launch-phase SEO surface once you have a property to index and measure—not pre-build ideation alone. SEO subphase covers analytics-backed tuning: queries, pages, sitemaps, and index status tied to getting found.
How it compares
Authenticated Search Console MCP integration, not a Google SERP scraper or generic web automation skill.
Common Questions / FAQ
Who is com.mcparmory/google-search-console for?
Builders using Claude Code, Cursor, or compatible MCP clients who own a Search Console property and want analytics and URL inspection inside agent sessions.
When should I use com.mcparmory/google-search-console?
Use it during Launch and Grow SEO work—after pages are live—to review queries, fix indexing, submit sitemaps, and inspect URLs before bigger content or technical changes.
How do I add com.mcparmory/google-search-console to my agent?
Configure a stdio MCP entry for uvx package mcparmory-google-search-console 1.0.3 or Docker ghcr.io/mcparmory/google-search-console:1.0.3, and complete Google OAuth or service credentials as required by the server’s GSC setup.