gsc-mcp
Google Search Console for your AI agent
A small, read-only Model Context Protocol server that gives Claude, Cursor, Claude Code and any MCP client access to Search Console: search analytics, period comparisons, sitemaps and URL inspection. Service-account auth, so no personal Google login on the machine running the agent.
Install
claude mcp add --transport stdio gsc \ -e GSC_SERVICE_ACCOUNT_FILE=~/.config/gcloud/gsc-service-account.json \ -- uvx --from git+https://github.com/Walma-Labs/gsc-mcp gsc-mcp
Create a service account in Google Cloud, enable the Search Console API, add the account's e-mail as a user on each property, point GSC_SERVICE_ACCOUNT_FILE at the JSON key. Full steps in the README.
Tools
| Tool | What it does |
|---|---|
list_sites | Properties the service account can see, with permission level |
search_analytics | Clicks, impressions, CTR and position by date, query, page, country, device or search appearance, with filters and pagination |
compare_periods | Two date ranges side by side with deltas, site-wide or per dimension |
list_sitemaps | Submitted sitemaps with status, errors and indexed counts |
inspect_url | URL Inspection: index status, canonical, last crawl, mobile and rich-result verdicts |
What to ask it
"Compare the last 28 days with the previous 28. Which pages lost the most clicks, and which queries on those pages dropped?" — "Queries with more than 500 impressions where we rank 11 to 20." — "Is /guides/mcp indexed, and what does Google consider the canonical?"
Who built it
Walma AI builds an EU-hosted AI gateway that runs Claude, GPT, MCP servers and skills inside a company's own Azure tenant, with policy, budgets and a full audit log. We use this server every week for our own SEO, behind Walma AI Hub, next to Google Ads, GA4 and Ahrefs. Our guides cover the rest of the marketing stack: best MCP servers for marketing and SEO, Google Ads MCP, Google Analytics MCP and the complete guide to MCP.
MIT licensed. © 2026 Walma AI AB.