gsc-mcp
Provides read-only access to Google Search Console data, including search analytics (clicks, impressions, CTR, position), sitemap status, and URL inspection.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gsc-mcpWhat are my top performing pages by clicks in the last 28 days?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gsc-mcp
A free, open-source Model Context Protocol server that gives Claude (or any other MCP client -- ChatGPT, Codex, Cursor) direct, read-only access to your Google Search Console data: search analytics (clicks/impressions/CTR/position), sitemap status, and URL inspection.
Built by GrowthLever because, as a marketer, I don't love the interface for Google's products -- Search Console, GA4, and Ads included. This lets me put my own translation layer on top of the raw data and ask Claude for the insight directly, instead of digging through Google's UI. It's free because the tool isn't the product -- the workflows I run on top of it are (see the bottom of this page).
Bring your own Google credentials
This runs entirely on your machine using a Google OAuth client you create in your own Google Cloud account. Your refresh token never leaves your disk, and no Search Console data ever passes through a server GrowthLever operates. There's no account to create with us, nothing to sign up for, nothing to trust us with. See SECURITY.md and PRIVACY.md for the full detail.
Related MCP server: SearchConsole.ai
What it exposes
Four read-only tools:
Tool | What it does |
| Lists the GSC properties the authorized account can access |
| Clicks/impressions/CTR/position, filterable by query, page, country, device, date |
| Submitted sitemaps and their status/errors |
| Index coverage, canonical URL, and crawl details for one URL |
Nothing here can change Search Console settings or submit/delete anything -- every call is a GET or a read-only query/inspect request.
Get started
QUICKSTART.md -- 10-minute setup, most of it waiting on Google's console. Short version:
npx -y @growthlever/gsc-mcp auth --credentials ~/Downloads/client_secret.json
npx -y @growthlever/gsc-mcp doctorThen point your Claude config at npx -y @growthlever/gsc-mcp (example in examples/claude-desktop-config.json) and ask it something -- see PROMPTS.md for a starter pack, split by founder-building-from-zero and scale-up-optimizing-what-works.
Something not working? Run gsc-mcp doctor first, then check TROUBLESHOOTING.md.
Local development
npm install
node bin/gsc-mcp.js auth --credentials <path to client_secret.json>
node bin/gsc-mcp.js doctor
node bin/gsc-mcp.js # runs the MCP server over stdio
node test/smoke.js # spawns the server and verifies tool registrationDocs
QUICKSTART.md -- setup, start to finish
PROMPTS.md -- starter prompt pack
SECURITY.md -- what this touches, what it can't do, how to revoke access
PRIVACY.md -- what's collected (nothing) and who sees your data
TROUBLESHOOTING.md -- plain-language fixes for common Google/OAuth errors
examples/ -- config for Claude Desktop and Codex CLI, plus a weekly-review prompt template
Why this is free
I'm a fractional Head of Growth -- most of the founders and operators I talk to are starting from scratch and didn't get into business to learn marketing. The best early move is almost always laying an organic foundation while referrals and word of mouth do the rest, because there isn't budget for paid yet. Scale-ups have a different problem: figuring out which pages and content are actually working so they can double down instead of guessing.
Either way, the blocker usually isn't access to data -- Search Console is free -- it's translating that data into "what do I do next." That's what this tool plus a decent prompt does. I'm giving the tool away because the tool isn't hard to build; the judgment about what to do with the output is where the actual value is, and that's what I write about and go deeper on for subscribers.
If you want the applied layer -- prompt packs by use case, weekly review and client-reporting templates, and the founder/scale-up workflows this is built around -- that's on Substack (subscriber content).
License
MIT. Fork it, self-host it, build on it.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.
Read Search Console performance, keyword opportunities and annotations for your sites.
Provides read access to your GKE and Kubernetes resources.
GA4, Google Ads and Search Console in Claude. Read-only OAuth, multi-account for agencies.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.105 npm1MIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server for Google Search Console data, enabling search analytics, URL inspection, indexing diagnostics, and sitemap management through MCP clients.7 npmMIT
- AlicenseBqualityAmaintenanceEnables MCP clients to query Google Search Console search performance, inspect indexing, analyze sitemaps, and run SEO analyses such as cannibalisation detection, query clustering, and wins/losses, all with read-only access.2073 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables read-only access to Google Search Console data, including property discovery, search analytics queries, and URL inspection, through a security-focused interface.3MIT