Add GSC PAP to Cursor

Steps

1. 1

   Sign in to GSC PAP

   Visit gscpap.com and click "Sign in with Google." Grant the read-only Search Console scope. The connect page shows your one-time bearer token - copy it. You will paste it into the Cursor config in step 3.

2. 2

   Open Cursor's MCP config file

   Cursor stores MCP server config in a single JSON file under your home directory. Open it in Cursor itself or any text editor. Create the file if it does not exist.

   shellCopy

   # macOS, Linux
   ~/.cursor/mcp.json
   
   # Windows
   %USERPROFILE%\.cursor\mcp.json

3. 3

   Add the GSC PAP server

   Paste the block below. Replace YOUR_TOKEN with the bearer from step 1. If the file already has other servers, just add the gsc-pap key inside mcpServers.

   jsonCopy

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

4. 4

   Reload Cursor's MCP servers

   Open Cursor settings (Cmd+, on macOS, Ctrl+, on Windows). Search for "MCP" - you will see the list of configured servers. Click the refresh icon next to gsc-pap. After a few seconds you should see a green "connected" indicator and the list of 18 available tools (list_sites, search_analytics_query, find_quick_wins, and the rest).

5. 5

   Use it in chat or agent mode

   Open Cursor's chat (Cmd+L). Type @ and pick gsc-pap to scope a question to your Search Console data, then ask: "What are my top queries by clicks this week?" Cursor calls the appropriate tool, gets your real GSC data back, and writes the answer inline. In agent mode (Cmd+I) the same tools are available without the @ prefix.

Common gotchas

• ·Cursor caches the MCP server list aggressively. If you change the config and the server does not show updated tools, fully quit Cursor (Cmd+Q) instead of using window close.
• ·If you see "Bearer token rejected," your token may have been revoked or the account deleted. Mint a fresh one from /account/tokens.
• ·Agent mode in Cursor sometimes ignores MCP tools when the conversation is long. Start a new chat if your queries stop reaching gsc-pap.
• ·Cursor on Windows occasionally writes the config file with BOM. If you get JSON parse errors, open the file and re-save as UTF-8 without BOM.