Connect Windsurf to Google Search Console

How to connect Google Search Console to Windsurf

1. 1

   Sign in to GSC PAP and copy your token

   Go to gscpap.com and click "Sign in with Google." Approve the read-only access it asks for. The connect page then shows your bearer token once, so copy it now. If you lose it, create a new one at app.gscpap.com/account/tokens; your other tokens keep working.

2. 2

   Add gsc-pap to the Devin Local config

   Devin Local reads MCP servers from the Devin CLI config files. For a server that works in every project, open or create ~/.config/devin/mcp_config.json (on Windows, %APPDATA%\devin\mcp_config.json) and add the block below with your token in place of YOUR_TOKEN. If the file already has an mcpServers object, add only the gsc-pap entry to it. Older builds kept mcpServers in ~/.config/devin/config.json; current builds move those entries into mcp_config.json automatically.

   jsonCopy

   {
     "mcpServers": {
       "gsc-pap": {
         "url": "https://mcp.gscpap.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_TOKEN"
         }
       }
     }
   }

3. 3

   Using the legacy Cascade agent? Add it there too

   Cascade reads a different file: ~/.codeium/windsurf/mcp_config.json. Add the same gsc-pap block there; Cascade accepts either url or serverUrl for remote servers. You can also reach Cascade's MCP list from the MCPs icon at the top right of the Cascade panel, or from Devin Settings > Cascade > MCP Servers. Skip this step if you only use Devin Local.

4. 4

   Open a new agent tab and ask

   Start a new Devin Local session and ask: "Use the gsc-pap MCP server. Show me my top 10 queries by clicks last week." Devin Local asks for approval before it calls any MCP tool; you can allow a single tool or every gsc-pap tool, for this session or permanently. To confirm the server loaded, choose Open customizations from the new-tab menu in an agent space, which lists the MCP servers the session has loaded.

Windsurf (Devin Desktop) MCP setup: common issues

• ·A tool call that fails with "Missing or invalid bearer token" means the token is wrong or was revoked. Create a new one at app.gscpap.com/account/tokens and update the config file.
• ·Cascade can use at most 100 tools at once across all MCP servers. If you run several servers, turn off the tools you do not need on each server's settings page.
• ·For Cascade on Enterprise plans, MCP has to be turned on in settings first, and team admins can restrict which servers are allowed. An allowlist entry must match the server key, gsc-pap, exactly.
• ·Cascade's mcp_config.json can read the token from an environment variable: write the header value as "Bearer ${env:GSC_PAP_TOKEN}".

Frequently asked questions