Skip to main content

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:

claude mcp add gsc -e GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json -- uvx scalably-gsc-mcp

Codex:

codex mcp add gsc --env GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json -- uvx scalably-gsc-mcp

Claude Desktop: download gsc-mcp.mcpb from the latest GitHub release and open it.

Setup

  1. In Google Cloud, create or pick a project and enable the Google Search Console API on it (APIs and Services, Library).
  2. Create a service account in that project and download its JSON key.
  3. 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), summary, result, proof, warnings, recovery. 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.

Metadata

Release files for scalably-gsc-mcp 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for scalably-gsc-mcp 1.0.1
File Size Uploaded Provenance
scalably_gsc_mcp-1.0.1.tar.gz 18.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for scalably-gsc-mcp 1.0.1
File Interpreter ABI Platform
scalably_gsc_mcp-1.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 31.9 kB

Release files / scalably_gsc_mcp-1.0.1.tar.gz

Download URL scalably_gsc_mcp-1.0.1.tar.gz
Size 18.9 kB
Tags Source
SHA-256 checksum
How to use checksums
30c47d364a3b9a5dd75ebd7c9884f7edf447b4b2c5df514869bd2ec40908b638
BLAKE2b-256 checksum
How to use checksums
f6e0ee8047b851c617123b9895ef3096bf255bb6d5048ea3a2644debcb669a0d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release files / scalably_gsc_mcp-1.0.1-py3-none-any.whl

Download URL scalably_gsc_mcp-1.0.1-py3-none-any.whl
Size 13.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2d19f9eb5dedc191de1145f924423fc6599b17609df45678d05f7f8c0c171648
BLAKE2b-256 checksum
How to use checksums
2cf0dfdade2076f53cd44506dd99cc77fce440d52e465bcc30796891d2d49140
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Security for scalably-gsc-mcp 1.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for scalably_gsc_mcp-1.0.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page