GSC MCP Server
ToolA Model Context Protocol server that connects Claude — or any MCP client — directly to the Google Search Console API, so SEO analysis happens in conversation instead of in a spreadsheet export.
Overview
Search Console holds the data that should drive most SEO decisions, but getting at it means the web UI's limited views or a CSV export that's stale the moment it lands. Neither fits how analysis actually happens.
This MCP server exposes Search Console as tools an AI client can call directly. Ask a question in natural language and the model queries the API, pulls the real numbers, and reasons over them — no export, no intermediate spreadsheet, no manual pivot.
It exposes four tools: enumerate every property the account can access, query search analytics broken down by query, page, country, device, date, or search appearance, list submitted sitemaps and their status, and run URL Inspection for index status, crawl info, and rich results.
Key Features
- list_sites — every GSC property the account can access
- search_analytics — clicks, impressions, CTR, and position
- Breakdowns by query, page, country, device, date, or search appearance
- list_sitemaps — submitted sitemaps and their processing status
- inspect_url — index status, crawl info, and rich-results detection
- OAuth authentication against a personal Google account
- Works with Claude or any MCP-compatible client
- Node.js and TypeScript, installable as a standard MCP server
Tech Stack
Architecture Highlights
Want your data inside Claude?
MCP servers let an AI client query your real systems directly. I build them for internal tools, APIs, and databases.
Start a Conversation