Search Console MCP

What search-console-mcp does

search-console-mcp gives MCP-compatible clients access to Google Search Console data in read-only mode. It can discover the properties available to the signed-in account, retrieve performance metrics, compare equivalent time periods, inspect individual URLs, check batches of URLs, and list submitted sitemaps.

The analytics interface supports clicks, impressions, click-through rate, and average position. Results can be grouped by dimensions such as query, page, date, country, or device, and can include traffic sources such as Google Discover. Search Console data generally trails by roughly two to three days and covers approximately 16 months of history.

Ten built-in MCP prompts provide guided analyses including SEO checkups, traffic-drop diagnosis, traffic decay, striking-distance queries, keyword opportunities, cannibalization, title and meta rewrites, refresh-versus-new decisions, internal-link planning, and indexing audits.

How it works

Run the login command to open Google’s sign-in flow in a browser. Authentication uses a desktop OAuth flow with PKCE and a localhost callback; Google issues the tokens directly to the local machine. After login, an MCP client starts the server through the npm package using standard input and output.

The signed-in account must have at least Restricted access to a Search Console property for it to appear in list_properties. Use the returned siteUrl value in later requests, since properties may be represented as either domain properties such as sc-domain:example.com or URL-prefix properties such as https://example.com/.

compare_periods performs the date arithmetic and returns current values, previous-period values, and deltas for pages or queries. This lets an agent investigate changes without calculating the comparison itself.

Setup and configuration

Sign in once with:

npx search-console-mcp-server login

Then register the server with an MCP client. For Claude Code:

claude mcp add gsc --scope user -- npx -y search-console-mcp-server

Clients using an mcpServers configuration can use:

{
  "mcpServers": {
    "gsc": {
      "command": "npx",
      "args": ["-y", "search-console-mcp-server"]
    }
  }
}

If the client cannot locate npx, configure the absolute path returned by which npx. Credentials are stored under ~/.search-console-mcp/credentials.json with restrictive file permissions. Running npx search-console-mcp-server logout removes them. Developers who prefer their own Google OAuth application can set SEARCH_CONSOLE_MCP_CLIENT_ID and SEARCH_CONSOLE_MCP_CLIENT_SECRET.

Tools and capabilities

• list_properties returns the Search Console properties accessible to the authenticated account.
• query_search_analytics retrieves performance metrics with selected dimensions, filters, and pagination.
• compare_periods compares a range with the preceding range of equal length and sorts page or query changes by movement.
• inspect_url reports Google’s index status, indexing reasons, selected canonical, latest crawl, and mobile or rich-result issues for one URL.
• inspect_urls checks up to 10 URLs in one request and reports per-URL errors inline.
• list_sitemaps returns submitted sitemaps, their statuses, and counts.

Limitations and notes

The server requests the webmasters.readonly Google scope. It cannot modify Search Console properties, submit sitemaps, or make other changes. Search Console’s reporting delay means the newest days may be absent, particularly yesterday’s data.

Tokens remain on the local machine, and API calls go directly from that machine to Google rather than through an MCP proxy. Re-running the login command allows the user to choose a different Google account. The client process must run under the same user account that performed authentication so it can access the local credentials.