GSCout

How to Connect Google Search Console to Windsurf

Add GSCout to Windsurf's Cascade as a remote MCP server and query your Search Console from the editor.

Time: 2 minutesSign-in: personal tokenAccess: read-only

Connector URL

https://gscout.vibiz.app/mcp

Want to try first? Use https://gscout.vibiz.app/mcp/demo: no sign-in, sample data.

Steps

  1. Sign in to GSCout with Google and pick your property.
  2. Create a personal token on the GSCout Setup page.
  3. In Windsurf, open Settings, then Cascade, then MCP servers, and edit mcp_config.json as below.
  4. Refresh the server list and ask Cascade: "What are my top movers this week?"

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "gscout": {
      "serverUrl": "https://gscout.vibiz.app/mcp",
      "headers": { "Authorization": "Bearer gsk_your_token" }
    }
  }
}

Good to know

  • Keep the token private: it gives read access to your GSCout data. Revoke it on the Setup page at any time.

What to ask Windsurf first

Troubleshooting

  • “No property is connected”: open gscout.vibiz.app/app/properties and pick one; the tool answer says the same.
  • Google says the app is unverified: choose Advanced, then Go to GSCout. Access is read-only.
  • 401 or “token expired”: remove the connector and add it again; your client will sign in once more.
  • Numbers differ from the Search Console chart: query rows exclude anonymized queries, see anonymized queries.

Other clients: Claude, ChatGPT, Cursor, Claude Code, Codex, Gemini CLI, Mistral Le Chat, VS Code