Data as of
Google Search Console MCP Server for Claude Code: Setup
Claude Code: This server connects MCP assistants to Google Search Console data and management actions.
What you can do with Google Search Console in Claude Code
Authenticated Search Console reporting and indexing checks, with optional property and sitemap management.
- Inspect crawl and indexing problems across URLs.
- Review sitemap errors and submit sitemaps.
- Filter performance by device or country.
Before you start: Google Search Console in Claude Code
- 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 Code configuration
Choose Claude Code configuration scope
For Google Search Console MCP Server, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.
Add Google Search Console MCP Server to Claude Code
Use the mcp-gsc entry below in mcpServers. Keep Google Search Console MCP Server's documented stdio connection fields and your other Claude Code entries.
Check Google Search Console MCP Server in Claude Code
Google Search Console MCP Server: Inspect claude mcp list and /mcp status.
Config file · Project scope: .mcp.json at the repository root
{
"mcpServers": {
"mcp-gsc": {
"type": "stdio",
"command": "/FULL/PATH/TO/uvx",
"args": [
"mcp-search-console"
],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "<Absolute path to downloaded desktop OAuth client JSON>"
}
}
}
}claude mcp add-json --scope project 'mcp-gsc' '{"type":"stdio","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 Code
Google Search Console's stored tool list documents 15 tools; compare it with Claude Code's connected tool list, because the stored list is not a live check.
- get_capabilities
For Google Search Console's get_capabilities, review the permission request and arguments in Claude Code before approval.
- list_properties
For Google Search Console's list_properties, review the permission request and arguments in Claude Code before approval.
- get_site_details
For Google Search Console's get_site_details, review the permission request and arguments in Claude Code before approval.
Retrieve information about a selected property.
- get_search_analytics
For Google Search Console's get_search_analytics, review the permission request and arguments in Claude Code before approval.
Report query and page metrics for a selected date range.
- get_performance_overview
For Google Search Console's get_performance_overview, review the permission request and arguments in Claude Code before approval.
Summarize property performance over a time period.
- compare_search_periods
For Google Search Console's compare_search_periods, review the permission request and arguments in Claude Code before approval.
Compare metrics between two date ranges.
- get_search_by_page_query
For Google Search Console's get_search_by_page_query, review the permission request and arguments in Claude Code before approval.
- get_advanced_search_analytics
For Google Search Console's get_advanced_search_analytics, review the permission request and arguments in Claude Code before approval.
- inspect_url_enhanced
For Google Search Console's inspect_url_enhanced, review the permission request and arguments in Claude Code before approval.
Inspect detailed indexing and crawl status for a URL.
- batch_url_inspection
For Google Search Console's batch_url_inspection, review the permission request and arguments in Claude Code before approval.
- check_indexing_issues
For Google Search Console's check_indexing_issues, review the permission request and arguments in Claude Code before approval.
- get_sitemaps
For Google Search Console's get_sitemaps, review the permission request and arguments in Claude Code before approval.
- list_sitemaps_enhanced
For Google Search Console's list_sitemaps_enhanced, review the permission request and arguments in Claude Code before approval.
Retrieve sitemap details including errors and warnings.
- manage_sitemaps
For Google Search Console's manage_sitemaps, review the permission request and arguments in Claude Code before approval.
Submit or delete a sitemap, subject to configuration.
- reauthenticate
For Google Search Console's reauthenticate, review the permission request and arguments in Claude Code before approval.
Restart browser OAuth login to authenticate again or switch accounts.
Troubleshooting Google Search Console in Claude Code
- If Google Search Console MCP Server fails to start, check uvx mcp-search-console (from uv, for Python tools), the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
- Google Search Console MCP Server: check GSC_OAUTH_CLIENT_SECRETS_FILE; keep credentials out of shared .mcp.json.
- Google Search Console MCP Server uses stdio here: Claude Code 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 Code troubleshooting lives in the /clients/claude-code guide.
Google Search Console MCP Server — details. Claude Code guide