Connect Kilo Code to Google Search Console

How to connect Google Search Console to Kilo Code

1. 1

   Sign in to GSC PAP

   Go to gscpap.com, click "Sign in with Google" and approve the read-only access, then choose which properties to authorize. If you plan to use the OAuth route in step 4 you do not need to copy a token at all.

2. 2

   Open the Kilo config file

   The global config is ~/.config/kilo/kilo.jsonc, which covers every project. A project can override it with ./kilo.jsonc, or ./.kilo/kilo.jsonc if the root is already taken. Project configuration takes precedence over global. The UI route is the Settings icon in the sidebar toolbar, then the Agent Behaviour tab, then MCP Servers.

   shellCopy

   # global
   ~/.config/kilo/kilo.jsonc
   
   # project
   ./kilo.jsonc        # or ./.kilo/kilo.jsonc

3. 3

   Add GSC PAP with a token

   Note the top-level key: it is mcp, not mcpServers. Paste the block and replace YOUR_TOKEN with a token from app.gscpap.com/account/tokens.

   jsonCopy

   {
     "mcp": {
       "gsc-pap": {
         "type": "remote",
         "url": "https://mcp.gscpap.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_TOKEN"
         },
         "enabled": true,
         "timeout": 15000
       }
     }
   }

4. 4

   Or let it do the OAuth handshake

   Kilo starts an OAuth 2.0 flow automatically when the server supports it, and GSC PAP does, including dynamic client registration. Drop the headers block and Kilo will send you through the consent screen instead, which leaves no token in your config at all.

   jsonCopy

   {
     "mcp": {
       "gsc-pap": {
         "type": "remote",
         "url": "https://mcp.gscpap.com/mcp",
         "enabled": true
       }
     }
   }

5. 5

   Ask a Search Console question

   In the VS Code extension you can also add a server from Settings, then MCP, then Add Server, then Remote (HTTP), filling in the URL and headers. Either way, start with "list my Search Console sites", then move to "show the queries where I rank between 5 and 20 with a CTR under 2%".

Kilo Code MCP setup: common issues

• ·The config key is mcp. The SSE example in Kilo's own docs uses mcpServers, which is the older shape; a remote server under mcpServers will be ignored.
• ·If you authenticate with a header and Kilo still tries an OAuth flow, set "oauth": false on the server entry so it uses the token you gave it.
• ·Project config overrides global. An edit that appears to do nothing usually means a project kilo.jsonc is shadowing it.
• ·The files are JSONC, so comments are allowed. Trailing commas are still a parse error.
• ·"Missing or invalid bearer token" is a token problem, not a transport problem. Mint a new one at app.gscpap.com/account/tokens.

Frequently asked questions