Google Search Console MCP

io.scalablyPublished by scalably.iov1.0.1Updated Oct 24, 2026

Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools.

VerifiedSTDIODesktop onlyWeb Search & Scraping Data & Analytics

Server details

Identifier: io.scalably/gsc-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to scalably.io. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.scalably%2Fgsc-mcp.svg)](https://sourceweft.com/mcp/io.scalably%2Fgsc-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local, read-only MCP server that lets an assistant query Google Search Console data: properties, Search Analytics, sitemaps and URL index status.

What you can do: List the Search Console properties the service account can read and list sitemaps for a property or read one sitemap. Query Search Analytics with filters, hourly data and automatic pagination past the 25,000-row cap. Inspect a single URL's index status, or inspect many URLs in a batch with client-side throttling. Every tool returns structured JSON with status, summary, result, proof and warnings, and partial results indicate where to continue.
When to use it: Useful for SEO and site-owner work where an assistant should pull search performance, sitemap and indexing data from Google Search Console without manual exports. Suited to read-only reporting and diagnostics rather than making changes in Search Console.
Requirements: Runs locally over stdio, installed with uvx from the PyPI package or as a Claude Desktop .mcpb bundle. Needs a Google Cloud project with the Search Console API enabled and a service-account JSON key, whose path is set in GOOGLE_APPLICATION_CREDENTIALS. Each Search Console property must be shared with the service account email. Optional variables set log level, retry backoff and API base URLs.

Before you install

Requires a Google service-account private key file; keep it protected and never set the test-only GSC_TEST_ACCESS_TOKEN in normal use. Access is read-only, but granting the service account access to a property exposes that property's data to the assistant. URL inspection is quota-limited (600 per minute, 2,000 per day per property) and the server does not track daily usage across calls, so you must count it yourself.

Installation

In SourceWeft

Open Google Search Console MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

bash

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

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

Codex:

bash

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

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

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: [email protected]. Canonical copy: https://scalably.io/connector-privacy.html

License

MIT. Copyright Scalably.

Source: README.md at commit 357b2eb

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts