Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON ▾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Google Search Console MCP, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
Google Search Console MCP
Read-only MCP server for Google Search Console. Five tools cover the read surface: properties, Search Analytics (filters, auto-pagination past the 25,000-row cap, hourly data), sitemaps, URL inspection, batch inspection with throttling. We run this server in production for every SEO client.
Install
Claude Code:
Codex:
Claude Desktop: download gsc-mcp.mcpb from the latest GitHub release and open it.
Setup
- In Google Cloud, create or pick a project and enable the Google Search Console API on it (APIs and Services, Library).
- Create a service account in that project and download its JSON key.
- Add the service account's email as a user on each Search Console property you want to query (Settings, Users and permissions). Full or restricted permission both work for reading.
No OAuth consent screen is needed; the server authenticates as the service account with the webmasters.readonly scope.
Tools (5)
| Tool | What it does |
|---|---|
gsc_list_sites | List the Search Console properties the service account can read |
gsc_query_search_analytics | Query Search Analytics with filters, auto-pagination and hourly data |
gsc_list_sitemaps | List sitemaps for a property or read one sitemap |
gsc_inspect_url | Inspect one URL's index status |
gsc_batch_inspect_urls | Inspect many URLs with client-side throttling |
Configuration
| Variable | Required | Purpose |
|---|---|---|
GOOGLE_APPLICATION_CREDENTIALS | yes | Path to a Google service-account JSON file with the Search Console read-only scope; share each property with the service account email |
GSC_LOG_LEVEL | no | INFO (default) or DEBUG |
GSC_RETRY_BASE_SECONDS | no | Base delay in seconds for the retry backoff on transient API errors (default 1) |
GSC_WEBMASTERS_BASE, GSC_SEARCHCONSOLE_BASE | no | Override the two Google API base URLs (used by the test suite to point at a local fake; leave unset in normal use) |
GSC_TEST_ACCESS_TOKEN | no | Test-suite only: a literal bearer token that bypasses the service account. Never set it in normal use |
Reply shape
Every tool returns JSON with status (succeeded, partial, no_op), operation, summary, target, result, proof, warnings, recovery. Failures surface as a tool error whose text is <code>: <message> <hint>. A partial status with proof.nextStartRow means: continue from that row.
Limits
25,000 rows per Search Analytics call (the server auto-paginates past it up to max_rows). URL inspection: Google allows 600 per minute and 2,000 per day per property. The server paces batch inspection client-side (default 8 requests per second) and warns when a batch exceeds the daily quota; it does not track daily usage across calls, so keep your own count.
Verify
Each release lists the package version, the .mcpb sha256 and the production commit it was derived from in CHANGELOG.md. CI runs the tests and a clean install of the built wheel on every push.
Privacy Policy
This server runs locally, on your machine, under your own credentials. It collects no personal data, contains no telemetry, stores nothing persistently, and talks only to the vendor API it wraps. No third party, including Scalably, receives your data. Contact: hello@scalably.io. Canonical copy: https://scalably.io/connector-privacy.html
License
MIT. Copyright Scalably.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Google Search Console MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/google-search-console-mcp-3)HTML Embed
<a href="https://allmcps.com/mcp/google-search-console-mcp-3"><img src="https://allmcps.com/api/badge/google-search-console-mcp-3?style=directory" alt="Google Search Console MCP on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
27Quality signal: Emerging · 27/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership8/20
Documentation & tools11/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.