GSCout

How to Connect Google Search Console to OpenAI Codex

Give Codex CLI read-only access to your Search Console data with GSCout's remote MCP server.

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. On the GSCout Setup page, create a personal token (Codex reads it from an environment variable).
  3. Export it in your shell: export GSCOUT_TOKEN=gsk_…
  4. Add the server to ~/.codex/config.toml as shown below, then restart Codex.
  5. Ask: "Which queries are cannibalized on my site?"

~/.codex/config.toml

[mcp_servers.gscout]
url = "https://gscout.vibiz.app/mcp"
bearer_token_env_var = "GSCOUT_TOKEN"

Good to know

  • Newer Codex versions can also sign in with OAuth: run codex mcp login gscout.

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