Record · mcp-gscMCP serverCosts not checkedRecord checked Sep 23, 2026

Google Search Console MCP (mcp-gsc)

Ask questions of your Google Search Console performance, indexing and URL inspection data.

Visit Google Search Console MCP (mcp-gsc) →View repository

Sources and review

Checked against public documentation on September 23, 2026. Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.

Repository and README

Best for

SEOs and site owners who want to interrogate their own Search Console data in conversation instead of exporting reports.

Avoid if

You can't create Google Cloud OAuth credentials or a service account; setup requires one.

About Google Search Console MCP (mcp-gsc)

mcp-gsc is a community MCP server that connects Google Search Console to AI assistants including Claude Desktop, Cursor, Codex CLI and Gemini CLI. Its tools cover search analytics by query and page, URL inspection with batch checks and rich-result issues, and indexing diagnostics. It authenticates with Google OAuth client secrets or a service account. The author also offers a separate hosted version.

Google Search Console MCP (mcp-gsc) is listed in this index written primarily in Python, with 2.1k stars on GitHub. Its latest recorded repository push was in September 2026; that is not an ASE editorial review date.

Before connecting: access and data

This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.

List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.

Read the setup guide →

Add Google Search Console MCP (mcp-gsc) to your MCP client

Generated from the launch command in the project's README. Your client starts the server on demand.

Claude CodeRun in your terminal

claude mcp add mcp-gsc -e GSC_OAUTH_CLIENT_SECRETS_FILE=/path/to/client_secrets.json -- uvx mcp-search-console

Cursor~/.cursor/mcp.json or .cursor/mcp.json

{
  "mcpServers": {
    "mcp-gsc": {
      "command": "uvx",
      "args": ["mcp-search-console"],
      "env": {
        "GSC_OAUTH_CLIENT_SECRETS_FILE": "/path/to/client_secrets.json"
      }
    }
  }
}

VS Code.vscode/mcp.json

{
  "servers": {
    "mcp-gsc": {
      "type": "stdio",
      "command": "uvx",
      "args": ["mcp-search-console"],
      "env": {
        "GSC_OAUTH_CLIENT_SECRETS_FILE": "/path/to/client_secrets.json"
      }
    }
  }
}

Claude Desktopclaude_desktop_config.json

{
  "mcpServers": {
    "mcp-gsc": {
      "command": "uvx",
      "args": ["mcp-search-console"],
      "env": {
        "GSC_OAUTH_CLIENT_SECRETS_FILE": "/path/to/client_secrets.json"
      }
    }
  }
}

Codex~/.codex/config.toml

[mcp_servers.mcp-gsc]
command = "uvx"
args = ["mcp-search-console"]
env = { GSC_OAUTH_CLIENT_SECRETS_FILE = "/path/to/client_secrets.json" }

Check the project's README for required accounts, keys and permissions before connecting. Setup guide for each client →

For agent buildersMake your product part of the discovery.Explore advertising