Log inSubmit server
Google Searchconsole MCP logo

Google Searchconsole MCP

by lionkiii

Connects AI clients to Google Search Console for SEO analytics, URL inspection, sitemap checks, and keyword analysis.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Searchconsole MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "lionkiii-google-searchconsole-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "google-searchconsole-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 13 tools correctly (1mo ago).

Overview

The lionkiii/google-searchconsole-mcp MCP server connects MCP-compatible AI clients to Google Search Console through read-only OAuth access. It provides tools for search analytics, URL inspection, sitemap listing, keyword opportunity detection, brand analysis, and period comparisons. Run it locally with Node.js and authenticate a Google account whose properties you want to query. Reach for it when an agent needs to investigate organic search performance or indexing without exporting Search Console data manually.

Use cases

  • Analyze top pages and search queries
  • Find high-impression, low-CTR keywords
  • Inspect URL indexing and mobile usability
  • Compare organic performance across periods
  • Export Search Console analytics for reporting

Key features

  • Google Search Console OAuth access
  • Search analytics by query, page, country, device, or date
  • URL indexing and rich-result inspection
  • Keyword opportunity and trend analysis
  • Sitemap listing
  • CSV and JSON analytics export

Tools13

What Google Searchconsole MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

19/19 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · google-searchconsole-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads1.7kPackage downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed13Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Google Searchconsole MCP works

What lionkiii/google-searchconsole-mcp MCP server does

The lionkiii/google-searchconsole-mcp MCP server exposes Google Search Console data and operations as MCP tools for AI clients. It focuses on SEO analysis and site diagnostics rather than changing website content or Search Console settings. The server can list authenticated accounts and accessible properties, retrieve search performance metrics, inspect individual URLs, and list submitted sitemaps.

Its analytics features cover clicks, impressions, click-through rate, and average position. Queries can be examined by dimensions such as search query, page, country, device, or date. Additional tools identify high-impression queries with relatively low CTR, rank pages by selected performance metrics, compare two date ranges, separate branded from non-branded traffic, and show a keyword’s daily trend. Results can also be exported as CSV or JSON.

How it works

The server runs locally and communicates with Google Search Console through the Google API. Initial authentication uses a browser-based Google OAuth flow. After the user grants read-only Search Console access, OAuth tokens are stored under ~/.gsc-mcp/tokens/. Search Console data is queried directly from Google rather than routed through an intermediary.

The package includes OAuth credentials for the standard setup, so a Google Cloud project is not required. It also supports an alternative configuration using a user-managed OAuth client ID and secret, or a credentials file stored at ~/.gsc-mcp/credentials.json.

Setup and configuration

The lionkiii/google-searchconsole-mcp MCP server requires Node.js 18 or newer and a Google account with access to Search Console. Install the npm package globally, then run gsc-mcp-auth to open the login flow. Separate account aliases can be supplied for users who need to authenticate multiple Google accounts, and the authentication command can list configured aliases.

For Claude Desktop, configure an MCP server entry that runs npx with the package name and the -y option. The README also identifies Cursor, Windsurf, VS Code with Cline, and other MCP-compatible clients as supported. Client configuration details may differ, but the process is to point the client at the local MCP process.

Tools and capabilities

The lionkiii/google-searchconsole-mcp MCP server includes 13 tools:

  • List Google accounts, Search Console properties, and submitted sitemaps.
  • Query analytics by dimensions, search appearance, or search type.
  • Inspect indexing state, crawl information, mobile usability, and rich-result details for a URL.
  • Find high-impression, low-CTR query opportunities.
  • Rank top pages by clicks, impressions, CTR, or position.
  • Compare performance between two periods and identify gains or losses.
  • Analyze branded versus non-branded queries.
  • Track daily metrics for a chosen keyword.
  • Export analytics results as CSV or JSON.

Limitations and notes

Access is read-only according to the authentication instructions, so the documented tools are for retrieving and analyzing Search Console information rather than submitting changes. The account used for OAuth must already have access to the relevant Search Console properties. The standard setup stores tokens locally, and the project states that it does not collect or transmit Search Console data to third parties.

Using custom OAuth credentials adds Google Cloud setup: a project, the Search Console API, and a desktop OAuth client are required.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Searchconsole MCP

Install Node.js 18 or newer, then install the npm package globally with `npm install -g google-searchconsole-mcp`.

Run `gsc-mcp-auth`. It opens a browser for Google sign-in and read-only Search Console authorization, then saves tokens locally under `~/.gsc-mcp/tokens/`.

Yes. The README provides a Claude Desktop configuration using `npx -y google-searchconsole-mcp`.

It can query clicks, impressions, CTR, and average position by dimensions including query, page, country, device, and date. It also supports search appearance and search type filters.

No for the standard setup: the package includes OAuth credentials. A user-managed Google Cloud OAuth project is supported as an alternative.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

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 PreviewGoogle Searchconsole MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/lionkiii-google-searchconsole-mcp?style=directory)](https://allmcps.com/mcp/lionkiii-google-searchconsole-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/lionkiii-google-searchconsole-mcp"><img src="https://allmcps.com/api/badge/lionkiii-google-searchconsole-mcp?style=directory" alt="Google Searchconsole MCP on AllMCPs" /></a>