Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
uvx scalably-gsc-mcp
MCP client config
{
"mcpServers": {
"google-search-console-mcp": {
"command": "uvx",
"args": [
"scalably-gsc-mcp"
]
}
}
}Distributed as an MCP bundle (`https://github.com/scalably-io/gsc-mcp/releases/download/v1.0.1/gsc-mcp.mcpb`) — download it and import the bundle in your MCP client.
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.
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.
No OAuth consent screen is needed; the server authenticates as the service account with the webmasters.readonly scope.
| 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 |
| 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 |
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.
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.
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.
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
MIT. Copyright Scalably.