Connect Claude Desktop to Google Search Console

How to connect Google Search Console to Claude Desktop

1. 1

   Install Claude Desktop

   Download Claude Desktop from claude.ai/download, open it, and sign in with your Anthropic account.

2. 2

   Sign in to GSC PAP and copy your token

   Visit gscpap.com and click "Sign in with Google." Grant the read-only Search Console access. The connect page 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.

3. 3

   Check that Node.js is installed

   The bridge runs through npx, which ships with Node.js. Open a terminal and run the command below. If it prints a version number you are set. If the command is not found, install the LTS version from nodejs.org, then continue.

   shellCopy

   node --version

4. 4

   Open the Claude Desktop config file

   Claude Desktop keeps its MCP servers in claude_desktop_config.json. Its Open Developer Config File command opens it for you, or open it directly at the path for your OS below. If the file does not exist yet, create it.

   shellCopy

   # macOS
   ~/Library/Application Support/Claude/claude_desktop_config.json
   
   # Windows
   %APPDATA%\Claude\claude_desktop_config.json

5. 5

   Add the GSC PAP server block

   Paste the block below and replace YOUR_TOKEN with the token from step 2, keeping the word Bearer and the space before it. If the file already has an mcpServers section, add gsc-pap inside it next to your other servers instead of pasting a second mcpServers. Leave "Authorization:${AUTH}" exactly as written: the bridge fills in AUTH from the env block, and keeping the space out of the argument avoids a known Windows problem with spaces in arguments.

   jsonCopy

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

6. 6

   Restart Claude Desktop and ask a question

   Quit Claude Desktop completely (Cmd+Q on macOS, or Quit from the tray icon on Windows) and open it again. The first start takes a little longer while npx downloads the bridge. Open a new chat and ask: "What sites are in my Search Console?" Claude calls list_sites and lists your verified properties. From there, try "Show me my top queries last week."

Claude Desktop not showing your Search Console data?

• ·Claude Desktop says "The following entries in claude_desktop_config.json are not valid MCP server configurations": an entry has the wrong shape. A block with "url" and "headers" produces exactly this, even though Cursor and other clients use that shape. Claude Desktop's config file only accepts servers it launches as a command, with command, args and env, which is why this guide uses the mcp-remote bridge.
• ·"npx: command not found" or the server never starts: Node.js is missing or not on Claude Desktop's PATH. Install the LTS from nodejs.org and restart Claude Desktop.
• ·GSC PAP tools do not appear, or Claude reports an authorization error: the token in AUTH is wrong or was revoked. Create a new one at app.gscpap.com/account/tokens and paste it into AUTH, with Bearer and a space in front, then restart Claude Desktop.
• ·Claude Desktop reports a config error: check the JSON for trailing commas or unmatched braces. Run the file through a JSON validator if unsure.
• ·On Windows, %APPDATA% expands to C:\Users\<you>\AppData\Roaming, which File Explorer hides by default. The Open Developer Config File command avoids hunting for it.

Frequently asked questions