Data as of

Google Search Console MCP Server for Claude Desktop: Setup

Claude Desktop: This server connects MCP assistants to Google Search Console data and management actions.

What you can do with Google Search Console in Claude Desktop

Authenticated Search Console reporting and indexing checks, with optional property and sitemap management.

  • Compare search traffic between reporting periods.
  • Find queries driving visits to a specific page.
  • Inspect crawl and indexing problems across URLs.

Before you start: Google Search Console in Claude Desktop

  • uv / uvx
  • Google project with Search Console API enabled
  • OAuth desktop client credentials or a service-account key
  • Access to the relevant Search Console property

Replace /FULL/PATH/TO/uvx with the actual executable path. This example uses OAuth and opens a browser on first use. Service-account setup instead uses GSC_CREDENTIALS_PATH and GSC_SKIP_OAUTH. The source-install path needs Python 3.11+.

Google Search Console Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For Google Search Console MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add Google Search Console MCP Server to Claude Desktop

    Use the mcp-gsc entry below in mcpServers. Keep Google Search Console MCP Server's documented stdio connection fields and your other Claude Desktop entries.

  3. Check Google Search Console MCP Server in Claude Desktop

    Google Search Console MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "mcp-gsc": {
      "command": "/FULL/PATH/TO/uvx",
      "args": [
        "mcp-search-console"
      ],
      "env": {
        "GSC_OAUTH_CLIENT_SECRETS_FILE": "<Absolute path to downloaded desktop OAuth client JSON>"
      }
    }
  }
}

Google Search Console tools available to Claude Desktop

Google Search Console's stored tool list documents 15 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

get_capabilities

When Claude Desktop requests get_capabilities from Google Search Console, review the action before approving it.

List available tools and report authentication status.

list_properties

When Claude Desktop requests list_properties from Google Search Console, review the action before approving it.

List the Search Console properties available to the account.

get_site_details

When Claude Desktop requests get_site_details from Google Search Console, review the action before approving it.

Retrieve information about a selected property.

get_search_analytics

When Claude Desktop requests get_search_analytics from Google Search Console, review the action before approving it.

Report query and page metrics for a selected date range.

get_performance_overview

When Claude Desktop requests get_performance_overview from Google Search Console, review the action before approving it.

Summarize property performance over a time period.

compare_search_periods

When Claude Desktop requests compare_search_periods from Google Search Console, review the action before approving it.

Compare metrics between two date ranges.

get_search_by_page_query

When Claude Desktop requests get_search_by_page_query from Google Search Console, review the action before approving it.

Find queries contributing traffic to a particular page.

get_advanced_search_analytics

When Claude Desktop requests get_advanced_search_analytics from Google Search Console, review the action before approving it.

Filter analytics by country, device, query, or page.

inspect_url_enhanced

When Claude Desktop requests inspect_url_enhanced from Google Search Console, review the action before approving it.

batch_url_inspection

When Claude Desktop requests batch_url_inspection from Google Search Console, review the action before approving it.

check_indexing_issues

When Claude Desktop requests check_indexing_issues from Google Search Console, review the action before approving it.

get_sitemaps

When Claude Desktop requests get_sitemaps from Google Search Console, review the action before approving it.

list_sitemaps_enhanced

When Claude Desktop requests list_sitemaps_enhanced from Google Search Console, review the action before approving it.

manage_sitemaps

When Claude Desktop requests manage_sitemaps from Google Search Console, review the action before approving it.

reauthenticate

When Claude Desktop requests reauthenticate from Google Search Console, review the action before approving it.

Google Search Console: full stored tool descriptions

Troubleshooting Google Search Console in Claude Desktop

  • Fully quit and reopen Claude Desktop for Google Search Console MCP Server. If uvx mcp-search-console (from uv, for Python tools) is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's Google Search Console MCP Server entry, check GSC_OAUTH_CLIENT_SECRETS_FILE. Keep secrets out of shared screenshots and repositories.
  • Google Search Console MCP Server uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires Google API credential setup and property access.
  • Known limitation: Batch URL inspection is limited to ten URLs per call.
  • Known limitation: Finalized data has a documented reporting lag.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Google Search Console MCP Server — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads Google Search Console MCP Server from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's mcp-gsc example uses stdio.

Google Search Console MCP Server's Claude Desktop configuration invokes uvx mcp-search-console (from uv, for Python tools).

Claude Desktop's Google Search Console MCP Server example references GSC_OAUTH_CLIENT_SECRETS_FILE. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Google Search Console MCP Server's stored list contains 15 tools, including get_capabilities, list_properties, get_site_details. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

Yes. The service-account method uses a JSON key, GSC_CREDENTIALS_PATH, and GSC_SKIP_OAUTH, with property access granted to that account.

Call get_capabilities to inspect available tools and current authentication status.

No. GSC_ALLOW_DESTRUCTIVE defaults to false and must be enabled for the listed destructive operations.