Data as of

Google Search Console MCP Server for Windsurf: Setup

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

What you can do with Google Search Console in Windsurf

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.
  • Filter performance by device or country.

Before you start: Google Search Console in Windsurf

  • 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 Windsurf configuration

  1. Choose Windsurf configuration scope

    For Google Search Console MCP Server, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

  2. Add Google Search Console MCP Server to Windsurf

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

  3. Check Google Search Console MCP Server in Windsurf

    Google Search Console MCP Server: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_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 Windsurf

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

get_capabilities

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for get_capabilities.

List available tools and report authentication status.

list_properties

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for list_properties.

List the Search Console properties available to the account.

get_site_details

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for get_site_details.

get_search_analytics

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for get_search_analytics.

get_performance_overview

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for get_performance_overview.

compare_search_periods

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for compare_search_periods.

Compare metrics between two date ranges.

get_search_by_page_query

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for get_search_by_page_query.

Find queries contributing traffic to a particular page.

get_advanced_search_analytics

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for get_advanced_search_analytics.

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

inspect_url_enhanced

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for inspect_url_enhanced.

batch_url_inspection

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for batch_url_inspection.

check_indexing_issues

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for check_indexing_issues.

get_sitemaps

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for get_sitemaps.

list_sitemaps_enhanced

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for list_sitemaps_enhanced.

Retrieve sitemap details including errors and warnings.

manage_sitemaps

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for manage_sitemaps.

Submit or delete a sitemap, subject to configuration.

reauthenticate

After refreshing Google Search Console in Windsurf settings, check Cascade's tool list for reauthenticate.

Restart browser OAuth login to authenticate again or switch accounts.

Google Search Console: full stored tool descriptions

Troubleshooting Google Search Console in Windsurf

  • Check uvx mcp-search-console (from uv, for Python tools) on the machine running Windsurf's MCP integration for Google Search Console MCP Server; refresh MCP and inspect Cascade's tools.
  • Check GSC_OAUTH_CLIENT_SECRETS_FILE for Google Search Console MCP Server; do not bypass a Windsurf permission error with a broad administrator token.
  • Google Search Console MCP Server uses stdio here: Windsurf 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 Windsurf troubleshooting lives in the /clients/windsurf guide.

Google Search Console MCP Server — details. Windsurf guide

Frequently asked questions

Windsurf reads Google Search Console MCP Server under mcpServers in ~/.codeium/windsurf/mcp_config.json on macOS/Linux; Windows uses %USERPROFILE%\.codeium\windsurf\mcp_config.json.

Windsurf's mcp-gsc example uses stdio.

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

Windsurf'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 Windsurf'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.

GUI clients may not inherit the shell path, so the README recommends the full executable path.