Skip to main content
Mythos

GSC MCP is a local stdio Model Context Protocol server that gives Claude read-only access to Google Search Console — four tools for site listing, search analytics, top queries, and top pages — built for use inside agentic content creation loops.

GSC MCP runs as a single-file Python script using 📝FastMCP. Auth uses Google Application Default Credentials, with no client secrets, no OAuth dance, and a startup identity log that prints the authenticated email to stderr so wrong-account logins surface immediately. The server is registered in ~/.claude.json as the gsc MCP server, and any Claude session inheriting that config gets four mcp__gsc__* tools.

The four tools cover the working surface. gsc_list_sites returns verified properties and permission levels. gsc_search_analytics is the full Search Analytics query — dimensions, filters with six operators, dates, all six GSC search types, row_limit up to 25000 per request. gsc_top_queries(site_url, days, limit, page_filter) and gsc_top_pages(site_url, days, limit, query_filter) are opinionated wrappers with UTC date math and a days >= 3 finalization guard for trailing-window use.

The motivation is augmentation, not analytics. Before GSC MCP, putting search performance data in front of Claude meant pulling CSVs from the GSC web UI and pasting them into context — too slow for any agent loop. With GSC MCP installed, query-level performance is one tool call away from the model writing or auditing the content, which is the precondition for closing the content-feedback loop without a human in the middle. A latent API bug surfaced during the build: the request body field for search type is searchType, not type — caught by an independent Codex code review after the multi-stage Claude review missed it. A parametrized regression test now locks the fix in across all six valid search types.

Before this, BotBrian could write about ranking strategy in the abstract. Now it can audit a real site, surface specific queries, and recommend specific moves. The gap between commentary and craft.

Contexts

Created with 💜 by One Inc | Copyright 2026