Connect Cursor to Google Search Console

How to connect Google Search Console to Cursor

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. You paste it into Cursor's config in step 3. If you lose it, create a new one at app.gscpap.com/account/tokens; your other tokens keep working.

2. 2

   Open Cursor's MCP config file

   For a server that works in every project, use the global mcp.json in your home directory. Create the file if it does not exist. Cursor also reads .cursor/mcp.json inside a project, but that file often ends up in git, so keep your token out of it (see the issues below).

   shellCopy

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

3. 3

   Add the GSC PAP server

   Paste the block below and replace YOUR_TOKEN with the token from step 1. If the file already lists other servers, add the gsc-pap entry inside the existing mcpServers object instead of pasting a second one.

   jsonCopy

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

4. 4

   Check that Cursor loaded the server

   Open Cursor Settings and go to Tools & MCPs. (Cursor's docs also describe this list under Customize in the sidebar.) Find gsc-pap and make sure its toggle is on. Once it connects, its tools, such as list_sites, search_analytics_query and find_quick_wins, become available to the agent.

5. 5

   Ask a Search Console question

   Open the agent chat and ask: "What are my top queries by clicks this week?" Cursor uses MCP tools from its Available Tools list when they fit the request, and you can also name a tool, for example "use list_sites". By default, Cursor asks for your approval before it runs an MCP tool.

Cursor MCP setup: common issues

• ·A tool call that fails with "Missing or invalid bearer token" means the token in mcp.json is wrong or was revoked. Create a new one at app.gscpap.com/account/tokens and paste it in.
• ·If gsc-pap does not appear after you save mcp.json, check the file for JSON mistakes such as a trailing comma, then toggle the server off and on, or restart Cursor.
• ·The URL must be exactly https://mcp.gscpap.com/mcp, including the /mcp path.
• ·To keep the token out of a project-level .cursor/mcp.json, write the header value as "Bearer ${env:GSC_PAP_TOKEN}". Cursor fills in ${env:NAME} in url and headers from its environment, so GSC_PAP_TOKEN has to be set in the environment Cursor starts from.

Frequently asked questions