Connect JetBrains AI Assistant to Google Search Console

How to connect Google Search Console to JetBrains AI Assistant

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

   Open the MCP settings

   Go to Settings > Tools > AI Assistant > Model Context Protocol (MCP) and click Add. You can also get there by typing / in the AI Assistant chat and choosing Add Command.

3. 3

   Paste the gsc-pap configuration

   In the New MCP Server dialog, choose the URL-based (remote) connection and paste the JSON below with your token in place of YOUR_TOKEN. Set the server level to Global so it is available in every project, then click OK and Apply. Apply starts the server.

   jsonCopy

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

4. 4

   Check the status and ask a question

   The Status column shows whether AI Assistant connected. Click the icon in that column to see the tools gsc-pap provides. Then open the AI Assistant chat and ask: "What sites are in my Search Console? Give me the top 5 queries by clicks last week." AI Assistant calls the tools when they fit, or you can type / to run one directly.

5. 5

   If authentication fails, use a local bridge

   Only needed if step 4 shows "Missing or invalid bearer token" even with a fresh token. JetBrains documents remote servers with a url only and does not mention headers, so if your build does not send the header, replace the entry with this STDIO configuration. It runs the open-source mcp-remote package through npx (Node.js required), which forwards requests to GSC PAP and adds the header. Keep Authorization:${AUTH_HEADER} without spaces; the value with the space goes in env.

   jsonCopy

   {
     "mcpServers": {
       "gsc-pap": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "https://mcp.gscpap.com/mcp",
           "--header",
           "Authorization:${AUTH_HEADER}"
         ],
         "env": {
           "AUTH_HEADER": "Bearer YOUR_TOKEN"
         }
       }
     }
   }

JetBrains MCP setup: common issues

• ·"Missing or invalid bearer token" means the server did not receive a valid token. Create a new one at app.gscpap.com/account/tokens; if a fresh token still fails, use the bridge in step 5.
• ·After you change a server's configuration, click Apply. To have new and changed servers start on their own, turn on Automatically enable new and changed MCP servers on the same settings page.
• ·To reconnect, select gsc-pap and click Reconnect. To stop it, clear its checkbox and click Apply.
• ·For logs, choose Help > Show Log in Finder (macOS) or Show Log in Explorer (Windows) and open the mcp folder. It holds one log per configured server.
• ·If your organization manages AI Assistant centrally, an administrator may have preconfigured MCP servers and turned off adding your own.

Frequently asked questions