Google Search Console MCP Server

It connects directly to your Google Search Console account via the official API, letting you access key data right from AI tools like Claude Desktop

Local serverstdioPython

What is the Google Search Console MCP server?

Google Search Console MCP server exists for a simple reason — assistants are far more useful when they can act on Google Search Console directly instead of describing what you should do. It connects directly to your Google Search Console account via the official API, letting you access key data right from AI tools like Claude Desktop or OpenAI Agents SDK and others.

What you get

This project provides a Model Context Protocol (MCP) server that allows Claude AI (via the Claude Desktop app) or others to interact with the Google Search Console API. You can use it to query performance data, inspect URLs, check indexing status, and more, directly from your Claude chat (or others).

  • Sites: — List accessible sites/properties in your Search Console account
  • Search Analytics: — Fetch search performance data (clicks, impressions, CTR, position) with various filters and dimensions
  • URL Inspection: — Inspect the status of a specific URL in the Google index, check its indexing status, and request indexing
  • Sitemaps: — List submitted sitemaps for a site
  • (Helper) — Get an overall site performance summary (derived from Search Analytics data)

Configuration and credentials

  • Python: Version 3.11 or higher. * pip: Python package installer (usually comes with Python). * Virtual Environment Tool: venv (recommended, built into Python 3). * Google Account: With access to the Google Search Console properties you want to query. * Claude Desktop App: Installed and running.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by metehan777; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the google search console mcp server does with a few real requests.

How to install the Google Search Console MCP server

{
      "mcpServers": {
        "filesystem": {
          "command": "npx",
          "args": [
            "-y",
            "@modelcontextprotocol/server-filesystem",
            "/Users/username/Desktop",
            "/Users/username/Downloads"
          ]
        },
        "google-search-console": {
          "command": "/Users/username/Documents/search-console-mcp/fresh_env/bin/python3",
          "args": [
            "-m",
            "main"
          ],
          "cwd": "/Users/username/Cursor/search-console-mcp"
        }
      }
    }

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Python: Version 3.11 or higher. * pip: Python package installer (usually comes with Python). * Virtual Environment Tool: venv (recommended, built into Python 3). * Google Account: With access to the Google Search Console properties you want to query. * Claude Desktop App: Installed and running.

Frequently asked questions

Python 3.11+, pip, a Google Account with Search Console access, and the Claude Desktop app installed and running.