Connect Continue to Google Search Console

How to add Google Search Console to Continue

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

   Save the token as a Continue secret

   Continue's IDE extensions cannot read environment variables from your shell, so store the token in Continue's global .env file. Create ~/.continue/.env (on Windows, %USERPROFILE%\.continue\.env) with the line below, using your token with no quotes around it. Keep this file out of version control.

   shellCopy

   GSC_PAP_TOKEN=YOUR_TOKEN

3. 3

   Add gsc-pap to config.yaml

   Open the Continue sidebar (Cmd/Ctrl+L in VS Code, Cmd/Ctrl+J in JetBrains), click the config selector above the chat input, and click the gear icon next to your local config. That opens ~/.continue/config.yaml. Add the gsc-pap item under mcpServers; if the file already has an mcpServers list, add only the item. Save the file and Continue reloads the config on its own.

   yamlCopy

   mcpServers:
     - name: gsc-pap
       type: streamable-http
       url: https://mcp.gscpap.com/mcp
       requestOptions:
         headers:
           Authorization: Bearer ${{ secrets.GSC_PAP_TOKEN }}

4. 4

   Ask in Agent mode

   Continue only uses MCP tools in Agent mode. Switch the chat to Agent and ask: "List my Search Console sites." Continue calls list_sites from gsc-pap and shows your verified properties.

Continue MCP config: common issues

• ·The older config.json format is deprecated. When config.yaml exists, Continue loads it instead of config.json, so add the server to config.yaml.
• ·"unresolved secrets: GSC_PAP_TOKEN" means Continue could not find the secret. Check that ~/.continue/.env exists and that the name matches exactly. Continue also looks in .env and .continue/.env at the workspace root.
• ·Instead of requestOptions.headers, you can write apiKey: ${{ secrets.GSC_PAP_TOKEN }} on the server entry. Continue sends apiKey as an Authorization: Bearer header.
• ·A "Missing or invalid bearer token" error means the token is wrong or was revoked. Create a new one at app.gscpap.com/account/tokens and update ~/.continue/.env.

Frequently asked questions