Google Search Console MCP server

<!-- mcp-name: io.github.acamolese/google-search-console-mcp -->

Google Search Console MCP

English · Italiano

Seventeen read-only tools over the Google Search Console API, plus a deterministic white-label HTML audit report an agency can put its own name on and send to a client, in English or Italian.

Regenerate that report from committed synthetic data, with no credentials:

python scripts/render_sample_report.py --lang en --open

Install

Claude Code

/plugin marketplace add acamolese/google-search-console-mcp
/plugin install google-search-console@acamolese

The plugin brings the MCP server, five skills (weekly review, cannibalisation check, indexing audit, content opportunities, white-label client audit) and a config prompt for the three credentials.

Claude Desktop

Download google-search-console.mcpb from the latest release and open it. It needs uv installed. Or edit the config file directly:

{
  "mcpServers": {
    "google-search-console": {
      "command": "uvx",
      "args": ["mcp-google-search-console"],
      "env": {
        "GSC_CLIENT_ID": "...",
        "GSC_CLIENT_SECRET": "...",
        "GSC_REFRESH_TOKEN": "..."
      }
    }
  }
}

Cursor, Codex, Gemini CLI, Zed

Any MCP client takes the same three lines: command uvx, argument mcp-google-search-console, and the three GSC_* environment variables.

# Codex
codex mcp add google-search-console -- uvx mcp-google-search-console

# Gemini CLI
gemini mcp add google-search-console uvx mcp-google-search-console

Docker

docker build -t mcp-gsc .
docker run --rm -p 127.0.0.1:8765:8765 \
  -e GSC_CLIENT_ID -e GSC_CLIENT_SECRET -e GSC_REFRESH_TOKEN \
  -v "$PWD/reports:/reports" mcp-gsc

The container speaks streamable HTTP on /mcp. It has no authentication of its own: keep it on loopback or behind a reverse proxy.

Authentication

The OAuth scope is webmasters.readonly and nothing else. No tool in this server can modify a property, a sitemap or anything else in Search Console.

Credentials are resolved in this order:

1. GSCAUTHMODE if set (oauth, service_account, adc)
2. GSCSERVICEACCOUNTFILE or GSCSERVICEACCOUNTJSON
3. GSCCLIENTID + GSCCLIENTSECRET + GSCREFRESHTOKEN
4. A token file in ~/.config/mcp-google-search-console/
5. Application Default Credentials

OAuth, once

Google Search Console API and create an OAuth client of type Desktop app.

1. In Google Cloud Console, enable the

~/.config/mcp-google-search-console/oauth_credentials.json:

1. Export the client, or save the downloaded JSON as

export GSC_CLIENT_ID="...apps.googleusercontent.com"
   export GSC_CLIENT_SECRET="..."
   uvx mcp-google-search-console auth

also stores a token at ~/.config/mcp-google-search-console/token.json with 0600 permissions.

1. The browser flow prints the three export lines for a stateless setup, and

On a headless machine, run auth on your laptop and copy the three environment variables across. --no-browser prints the URL instead of opening one, but still needs a local redirect.

Service account

Shortened. The full README is on GitHub.