MCP Google Search Console
Connect Google Search Console to your agent for queries, sitemaps, and URL inspection while you launch and tune SEO.
Overview
MCP Google Search Console is a MCP server for the Launch phase that lets your agent read GSC analytics, manage sitemaps, and run URL inspection for SEO fixes.
What is this MCP server?
- Secure MCP server for Google Search Console analytics and reporting
- Sitemap management and URL inspection exposed to the agent
- stdio PyPI package mcp-google-search-console-crunchtools v0.1.0
- Crunchtools repo github.com/crunchtools/mcp-google-search-console
- Built for post-ship visibility tuning, not pre-launch guesswork
- Server version 0.1.0
- PyPI identifier mcp-google-search-console-crunchtools
- Transport type stdio
What problem does it solve?
Exporting Search Console screens manually makes it hard for your agent to tie indexing errors to actual code and config changes.
Who is it for?
Indie hackers with a live site in Search Console who want agent-assisted technical SEO and reporting.
Skip if: Pre-launch projects with no verified property or builders who only need generic SEO copy skills without GSC data.
What do I get? / Deliverables
After install, the agent can pull GSC metrics and inspection results so you iterate titles, sitemaps, and routes with evidence.
- Agent-accessible GSC performance and query analytics
- Sitemap and URL inspection workflows callable from the IDE
- Evidence-backed SEO change lists tied to live search data
Recommended MCP Servers
Journey fit
Search Console data matters after you have something to index; Launch is where organic discovery and technical SEO decisions land. SEO is the canonical subphase for GSC analytics, sitemap health, and URL-level search diagnostics.
How it compares
MCP analytics integration for Google Search Console, not a keyword research skill or rank-tracking SaaS.
Common Questions / FAQ
Who is io.github.crunchtools/google-search-console for?
Solo builders and developers using MCP agents who operate a verified Google Search Console property and want data-driven SEO edits.
When should I use io.github.crunchtools/google-search-console?
After launch when you optimize indexing, sitemaps, and query performance and want the agent to ground suggestions in real GSC metrics.
How do I add io.github.crunchtools/google-search-console to my agent?
Install mcp-google-search-console-crunchtools from PyPI, configure stdio MCP, and authenticate to Google Search Console APIs per the crunchtools README.