Google Search Console MCP Server for VS Code: Setup & Config

What you can do with Google Search Console in VS Code

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

• Find queries driving visits to a specific page.
• Inspect crawl and indexing problems across URLs.
• Review sitemap errors and submit sitemaps.

Before you start: Google Search Console in VS 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 VS Code configuration

1. Choose VS Code configuration scope

   For Google Search Console MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Google Search Console MCP Server to VS Code

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

3. Check Google Search Console MCP Server in VS Code

   Google Search Console MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "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 VS Code

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

get_capabilities

Look for get_capabilities among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

list_properties

Look for list_properties among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

List the Search Console properties available to the account.

get_site_details

Look for get_site_details among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

Retrieve information about a selected property.

get_search_analytics

Look for get_search_analytics among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

Report query and page metrics for a selected date range.

get_performance_overview

Look for get_performance_overview among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

Summarize property performance over a time period.

compare_search_periods

Look for compare_search_periods among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

get_search_by_page_query

Look for get_search_by_page_query among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

get_advanced_search_analytics

Look for get_advanced_search_analytics among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

inspect_url_enhanced

Look for inspect_url_enhanced among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

Inspect detailed indexing and crawl status for a URL.

batch_url_inspection

Look for batch_url_inspection among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

Inspect up to ten URLs in one request.

check_indexing_issues

Look for check_indexing_issues among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

Check several URLs for indexing problems.

get_sitemaps

Look for get_sitemaps among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

List sitemaps for a property.

list_sitemaps_enhanced

Look for list_sitemaps_enhanced among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

manage_sitemaps

Look for manage_sitemaps among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

reauthenticate

Look for reauthenticate among VS Code's agent-mode tools after starting Google Search Console through the MCP controls.

Google Search Console: full stored tool descriptions

Troubleshooting Google Search Console in VS Code

• Make uvx mcp-search-console (from uv, for Python tools) available in the workspace, container, or remote environment hosting Google Search Console MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
• For Google Search Console MCP Server, keep GSC_OAUTH_CLIENT_SECRETS_FILE out of version control; VS Code documents input variables and secret handling.
• Google Search Console MCP Server uses stdio here: VS 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions