GSCout

How to Connect Google Search Console to Cursor (MCP Setup)

Add Google Search Console data to Cursor through GSCout's remote MCP server. Great for fixing titles and content right where the site's code lives.

Time: 1 minuteSign-in: OAuth in the clientAccess: 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. In Cursor, open Settings, then MCP, and click "Add new global MCP server" (this opens ~/.cursor/mcp.json).
  3. Add the GSCout server shown below and save.
  4. Cursor shows a "Needs login" button next to GSCout: click it and approve read-only access.
  5. In the agent chat, ask: "Find CTR gaps on my site and rewrite those pages' titles in this repo."

~/.cursor/mcp.json

{
  "mcpServers": {
    "gscout": { "url": "https://gscout.vibiz.app/mcp" }
  }
}

Good to know

  • Cursor supports remote MCP servers with OAuth, so no token is pasted anywhere.

What to ask Cursor 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, Claude Code, Codex, Windsurf, Gemini CLI, Mistral Le Chat, VS Code