Connect Roo Code to Google Search Console

How to connect Google Search Console to Roo Code

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, pick the sites you want to expose, and copy the bearer token the connect page shows once. More, each scoped to a subset of your sites, are at app.gscpap.com/account/tokens.

2. 2

   Open Roo's MCP settings file

   Click the MCP icon in the top navigation of the Roo Code pane, scroll to the bottom of the MCP settings view, and click Edit Global MCP for mcp_settings.json or Edit Project MCP for .roo/mcp.json in the project root. Roo creates the project file if it does not exist. If both files define a server with the same name, the project one wins.

3. 3

   Add the GSC PAP server

   Paste the block below and replace YOUR_TOKEN. The type is required and it is spelled streamable-http, with a hyphen.

   jsonCopy

   {
     "mcpServers": {
       "gsc-pap": {
         "type": "streamable-http",
         "url": "https://mcp.gscpap.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_TOKEN"
         },
         "disabled": false
       }
     }
   }

4. 4

   Optional: auto-approve the read tools

   alwaysAllow takes a list of tool names Roo may call without asking each time. Nothing GSC PAP exposes can change a property, so auto-approving its tools removes a confirmation per call without giving the agent a way to break something.

   jsonCopy

         "alwaysAllow": [
           "list_sites",
           "search_analytics_query",
           "find_quick_wins",
           "compare_periods"
         ]

5. 5

   Ask a Search Console question

   Open a Roo task and ask: "Use gsc-pap to list my sites, then show the top 10 queries by clicks over the last 28 days." The first call is always list_sites, because the other tools need the exact property URL it returns.

Roo Code MCP setup: common issues

• ·The transport is "streamable-http" with a hyphen. Cline spells the same thing "streamableHttp", so a config copied between the two will not connect until you change it.
• ·A project .roo/mcp.json overrides a global entry with the same server name. If an edit to the global file seems to do nothing, look for a project file shadowing it.
• ·Put the token in the global mcp_settings.json rather than .roo/mcp.json if the project is a git repo, or you will be rotating a committed token.
• ·"Missing or invalid bearer token" means the token is wrong or revoked, not that the transport is wrong. Replace it at app.gscpap.com/account/tokens.
• ·timeout and disabledTools also work on this transport, which is useful when you want only part of a 34-tool server in context.

Frequently asked questions