Index live · v1.7.0 · NOV 18 2026

GSC MCP

Community

GSC MCP gives an agent your Search Console data and a set of ready-made analyses on top of it: period comparisons, traffic-drop and content-decay checks, keyword cannibalization, indexing and page audits, URL inspection, and report exports. It runs locally over stdio, and Google API calls go straight from your machine to Google. Access is read-only by default and limited to the properties you name in `GSC_SITE_URLS`. Quick Connect signs you in through a shared read-only OAuth client shipped in the package, so you don't create a Google Cloud project; the sign-in tokens stay on your machine in `~/.gsc-mcp/`. Writing (submitting URLs and sitemaps) needs your own OAuth client or a service account plus `GSC_ACCESS_MODE=full`, and setup asks before enabling it. URL Inspection reads Google's indexed view; it does not request indexing. Needs Node.js 22 or newer.

Not tested by usIt needs a Google account with access to a Search Console property, which our test machine doesn't have, so we didn't use it ourselves. We reviewed its code and security, checked that it installs where it can, and looked for signs that other people use it.
stdioTypeScriptOAuth
4stars

Configuration

claude mcp add gsc-mcp -e GSC_AUTH_MODE=oauth -e GSC_ACCESS_MODE=readonly -e GSC_SITE_URLS=sc-domain:example.com -- npx -y @sonnivasquez/gsc-mcp

Run in a terminal. Copied verbatim from the upstream README.

Quick Stats

Trust LevelCommunity
Stars4
Transportstdio
AuthOAuth
LanguageTypeScript
CategoryAnalytics & Monitoring

Tags

seosearch-consolegooglesearch-analyticsread-only

Get new MCP servers in your inbox. What we added, what failed the security audit, and why. See a past issue.