Skip to content
MCP server

Google Search Console MCP

Search Console clicks, positions, URL inspection and sitemaps for your AI agent

Runs locallyStatus and history
Pricing
Open source
Platforms
vscode, CLI
Runs
Locally
Version
26.11.14
Listing updated
2 days ago

About Google Search Console MCP

Google Search Console MCP is an open-source MCP server for web search and scraping. It runs locally on your machine and is started by your AI client.

This is a local server, shipped as a VS Code extension and as an npm package, that calls Google's Search Console API with your own credentials. Its search analytics tool returns the same data as the Performance report without the screen's 1,000 row limit, up to 25,000 rows per call, grouped by query, page, country, device or date, with web, image, video, news and Discover search types.

Typical questions are which searches rank between positions 8 and 20, which pages lost clicks month over month, and whether a new URL is indexed. URL inspection reports Google's indexed version, not a live test, and it cannot request indexing. Two Indexing API tools notify Google about updated or removed URLs; Google documents that API for job posting and livestream pages.

Search Console data runs two to three days behind. The extension registers itself with Claude Code, Cursor, Codex, Gemini, Windsurf, Continue.dev, Cline and Copilot, and sign-in is OAuth, a service account key or gcloud Application Default Credentials. Outside VS Code it needs Node.js 22 or newer.

Install

Run in a terminal

claude mcp add google-search-console-mcp --env GOOGLE_OAUTH_CLIENT_SECRET='<GOOGLE_OAUTH_CLIENT_SECRET>' --env GOOGLE_OAUTH_REFRESH_TOKEN='<GOOGLE_OAUTH_REFRESH_TOKEN>' -- npx -y @renzo.johnson/google-search-console-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "google-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
        "GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "google-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
        "GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "google-search-console-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
        "GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "google-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
        "GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "google-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-search-console-mcp"
      ],
      "env": {
        "GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>",
        "GOOGLE_OAUTH_REFRESH_TOKEN": "<GOOGLE_OAUTH_REFRESH_TOKEN>"
      }
    }
  }
}

Configuration

  • GOOGLE_APPLICATION_CREDENTIALSPath to a service account key or authorized_user JSON file. Optional if you use gcloud Application Default Credentials or the OAuth variables.
  • GOOGLE_OAUTH_CLIENT_IDOAuth client ID. Set together with the client secret and refresh token.
  • GOOGLE_OAUTH_CLIENT_SECRETOAuth client secret.
  • GOOGLE_OAUTH_REFRESH_TOKENOAuth refresh token with the Search Console and Indexing API scopes.

Tools this server provides (8)

Taken from the project documentation; the running server may differ.

gsc_list_sites
List Search Console properties your account can open.
gsc_search_analytics
Query clicks, impressions, CTR and position.
gsc_inspect_url
Inspect a URL's index status and crawl details.
gsc_list_sitemaps
List sitemaps for a property.
gsc_submit_sitemap
Submit a sitemap.
gsc_add_site
Add a property.
indexing_notify
Tell Google a URL was updated or removed.
indexing_status
Show the last notification for a URL.

What it does

Search analytics
Clicks, impressions, CTR and position, grouped and filtered, up to 25,000 rows per call.
URL inspection
Index status, crawl details, mobile usability and rich results for one URL.
Sitemap management
List and submit sitemaps for a property.
Property listing
List and add properties by URL prefix or domain.
Indexing API
Notify Google of updated or removed URLs and read the last notification.
Runs locally
Calls Google with your credentials and has no telemetry.

Good for

  • Find searches ranking between positions 8 and 20
  • Find pages that lost clicks since last month
  • Check a page is indexed after publishing
  • Submit a new sitemap
  • Spot two pages competing for the same query

Pricing

Open source

Free, MIT licensed

Prices change. Check renzojohnson.com before you buy.

Google Search Console MCP FAQ

Is it free?

Yes, it is MIT licensed and Google does not charge for the API.

Which agents does it work with?

Claude Code, Cursor, Codex, Gemini, Windsurf, Continue.dev, Cline and VS Code Copilot.

Why does a property say not found?

Use the exact property name: a trailing-slash URL prefix or sc-domain:example.com.

Where does my data go?

Only to Google; the server runs on your machine.

Is Google Search Console MCP free?

Yes. Google Search Console MCP is open source, so you can use and self-host it for free.

How do I add Google Search Console MCP to Claude Code?

Run this command in your terminal: claude mcp add google-search-console-mcp --env GOOGLE_OAUTH_CLIENT_SECRET='<GOOGLE_OAUTH_CLIENT_SECRET>' --env GOOGLE_OAUTH_REFRESH_TOKEN='<GOOGLE_OAUTH_REFRESH_TOKEN>' -- npx -y @renzo.johnson/google-search-console-mcp

What are the best alternatives to Google Search Console MCP?

The closest alternatives to Google Search Console MCP are Scrapling MCP Server, Firecrawl MCP Server, Agent-Native Analytics, Google Ads + Meta Ads + SEO/GEO MCP and SearXNG Search.

Alternatives to Google Search Console MCP

  1. MCP server for AI clients to scrape sites with HTTP and stealth browser sessions

    Runs locally
    • 17 tools
    • Open source
    • 104K GitHub stars
    • Web search and scraping
  2. MCP server that lets AI agents search, scrape and interact with web pages

    • 3 tools
    • Remote
    • Freemium
    • 7.8K GitHub stars
    • Web search and scraping
  3. Open-source analytics app where an AI agent builds charts and dashboards from your data

    • Remote
    • Open source
    • 7.7K GitHub stars
    • Analytics and data
  4. Hosted MCP connector for managing Google Ads, Meta Ads, GA4 and Search Console from chat

    • 8 tools
    • Remote
    • Freemium
    • 8.1K GitHub stars
    • Marketing and SEO
  5. SearXNG Search

    MCP server

    MCP server for web search and page reading through a SearXNG instance

    Runs locally
    • 3 tools
    • Open source
    • 1.4K GitHub stars
    • Web search and scraping
  6. Indian NSE and BSE stock market data for AI assistants through 48 MCP tools

    • 17 tools
    • Remote
    • Freemium
    • 150 GitHub stars
    • Finance and payments