Search Console, inside the conversation

A remote MCP server that gives Claude read access to your Google Search Console data, so you can ask about rankings, indexing and site health in plain language instead of exporting spreadsheets.

https://gscmcp.santo.berlin/mcp

What it can do

• list_sites — properties this account can reach, with permission levels
• search_analytics — clicks, impressions, CTR and position, filtered and compared
• search_insights — near-miss rankings, weak CTR, competing pages, movers
• search_chart — daily performance as a chart plus the underlying table
• inspect_url — index status, canonical, last crawl, mobile and rich results
• list_sitemaps — submitted sitemaps with errors and warnings
• submit_sitemap — submit or resubmit a sitemap (needs write approval)
• delete_sitemap — withdraw a sitemap submission (needs write approval)
• list_notes — context saved from earlier sessions
• add_note — record a migration date, a brand term, a decision
• delete_note — remove a saved note
• page_speed — Core Web Vitals from real Chrome users, plus a lab score
• check_dns — A, AAAA, CNAME, MX, TXT, NS and CAA records
• check_redirects — the full hop-by-hop chain, loops included
• check_robots — whether a crawler may fetch a path, and the rule that decides
• check_tls — certificate issuer, expiry, coverage and chain validity

What it asks for

Sign-in requests read-only access to Search Console. Submitting or removing a sitemap is the only thing that writes to your account, and it stays unavailable until you grant that separately from your account page.

Your Google refresh token is encrypted before it is stored and is only ever used to answer your own tool calls. The four site-check tools read public web data and never touch your Google account.