---
title: "Google Search Console MCP Server for Cursor · GSC PAP"
source: https://gscpap.com/integrations/cursor
updated: 2026-09-18
---

[All integrations](https://gscpap.com/integrations)

Integration · Cursor

# Connect Cursor to Google Search Console

5 steps · about 5 minutes

By the [GSC PAP team](https://gscpap.com/about) · Updated September 18, 2026

Cursor is an AI code editor whose agent can call Model Context Protocol (MCP) tools. Add GSC PAP as a remote MCP server and the agent can read your Search Console clicks, impressions, CTR and average position without leaving the editor.

Once it is connected, you can ask things like "compare my top queries this week vs. last week" or "find pages where impressions dropped 20% in the last 30 days" in the same place you edit those pages.

This guide assumes you have Cursor installed and are signed in. If not, download it from cursor.com.

## How to connect Google Search Console to Cursor

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.  ### 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).
    
    ```shell
    # macOS, Linux
    ~/.cursor/mcp.json
    
    # Windows
    %USERPROFILE%\.cursor\mcp.json
    ```
    
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.
    
    ```json
    {
      "mcpServers": {
        "gsc-pap": {
          "url": "https://mcp.gscpap.com/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN"
          }
        }
      }
    }
    ```
    
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.  ### 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

### Do I need a Google Cloud project to use Search Console in Cursor?

No. Running your own Search Console MCP server means creating a Google Cloud project, enabling the Search Console API, creating OAuth credentials, and looking after a JSON credentials file and refresh tokens. GSC PAP is already hosted: you sign in with Google at gscpap.com, copy one bearer token, and paste it into ~/.cursor/mcp.json.

### Is the GSC PAP MCP server free to use with Cursor?

Yes, while GSC PAP is in public preview. There is no credit card, no trial that runs out, and no paid tier holding tools back. Usage is capped at 60 MCP tool calls per minute and 1,000 per hour per user.

### Why doesn't Cursor show the gsc-pap tools after I edit mcp.json?

Check that the file is valid JSON and that the gsc-pap entry sits inside mcpServers. Then open Tools & MCPs in Cursor Settings, make sure gsc-pap is toggled on, and restart Cursor if it still shows no tools. If the server reports a token error, create a new token at app.gscpap.com/account/tokens.

## Other integrations

[All integrations](https://gscpap.com/integrations)

[

### Claude Desktop

Connect Claude Desktop to Google Search Console without creating a Google Cloud project. Sign in with Google, paste one config block, restart Claude.

6 steps · 6 min read

](https://gscpap.com/integrations/claude-desktop)[

### Claude Code

Add Google Search Console to Claude Code with one claude mcp add command. Hosted and read-only: no Google Cloud project, no OAuth credentials, no Python.

3 steps · 3 min read

](https://gscpap.com/integrations/claude-code)[

### Codex CLI (OpenAI)

Add Google Search Console, GA4 and PageSpeed data to OpenAI's Codex CLI with one TOML block and a bearer token. You never create a Google Cloud project.

4 steps · 4 min read

](https://gscpap.com/integrations/codex-cli)[

### VS Code (GitHub Copilot)

Connect Google Search Console to GitHub Copilot in VS Code with one .vscode/mcp.json entry, then ask agent mode about GSC. You skip Google Cloud setup.

4 steps · 4 min read

](https://gscpap.com/integrations/vscode-copilot)[

### Gemini CLI (Google)

Query Google Search Console (GSC) from your terminal with Gemini CLI. Register GSC PAP as an MCP server in settings.json, with no Google Cloud project.

5 steps · 5 min read

](https://gscpap.com/integrations/gemini-cli)[

### Windsurf (Devin Desktop)

Give Windsurf, now Devin Desktop, your Google Search Console data. Add GSC PAP as a remote MCP server with one bearer token and no Google Cloud project.

4 steps · 5 min read

](https://gscpap.com/integrations/windsurf)[

### Zed Editor

Bring Google Search Console into Zed's AI assistant as an MCP context server. You add one settings.json block and a token, with no Google Cloud setup.

3 steps · 4 min read

](https://gscpap.com/integrations/zed)[

### JetBrains IDEs

Connect Google Search Console to IntelliJ, PyCharm, WebStorm and other JetBrains IDEs via AI Assistant's MCP settings, without a Google Cloud project.

5 steps · 5 min read

](https://gscpap.com/integrations/jetbrains)[

### Continue (extension)

Continue MCP setup for Google Search Console: add one mcpServers entry with a bearer token in VS Code or JetBrains. You do not need a Google Cloud project.

4 steps · 4 min read

](https://gscpap.com/integrations/continue)[

### Claude.ai (browser)

Add Google Search Console to Claude.ai as a custom connector. Paste one URL and approve access. No token to copy, no config file, no Google Cloud project.

3 steps · 3 min read

](https://gscpap.com/integrations/claude-ai-connectors)[

### Direct HTTP (curl, custom agents)

Call the GSC PAP MCP server from curl or your own agent. It is JSON-RPC over HTTP with a bearer token, so you need no MCP client or Google Cloud project.

4 steps · 5 min read

](https://gscpap.com/integrations/mcp-direct)[

### opencode

Add Google Search Console to opencode as a remote MCP server. One config block with your token, no Google Cloud project, no local server to run.

5 steps · 5 min read

](https://gscpap.com/integrations/opencode)[

### Cline

Add Google Search Console to Cline in VS Code or the Cline CLI as a remote MCP server. One token, no Google Cloud project, read-only access.

5 steps · 5 min read

](https://gscpap.com/integrations/cline)[

### Warp

Add Google Search Console to Warp's agent as a remote MCP server. Paste one JSON block with your token, press Start, and ask about your traffic in the terminal.

5 steps · 4 min read

](https://gscpap.com/integrations/warp)[

### LM Studio

Give a local model your Search Console data. Add GSC PAP to LM Studio's mcp.json as a remote server, with one token and no Google Cloud project.

5 steps · 5 min read

](https://gscpap.com/integrations/lm-studio)[

### ChatGPT

Add Google Search Console to ChatGPT as a custom MCP server. What the setup looks like, and the plan requirement that decides whether you can do it at all.

5 steps · 6 min read

](https://gscpap.com/integrations/chatgpt)[

### Goose

Add Google Search Console to Goose as a streamable_http extension. One block in config.yaml with your token, no Google Cloud project, read-only access.

5 steps · 5 min read

](https://gscpap.com/integrations/goose)[

### Google Antigravity

Add Search Console to Google Antigravity as a custom MCP server. It handles dynamic client registration, so the setup is a URL and a sign-in, with no token.

5 steps · 5 min read

](https://gscpap.com/integrations/antigravity)[

### Roo Code

Add Google Search Console to Roo Code in VS Code as a streamable-http MCP server. One block with your token, no Google Cloud project, read-only.

5 steps · 5 min read

](https://gscpap.com/integrations/roo-code)[

### Kilo Code

Add Google Search Console to Kilo Code as a remote MCP server. It can negotiate OAuth for you, or take a bearer token. No Google Cloud project either way.

5 steps · 5 min read

](https://gscpap.com/integrations/kilo-code)[

### Amp

Add Google Search Console to Amp as a remote MCP server, in settings or with one CLI command. No Google Cloud project, read-only scopes.

5 steps · 5 min read

](https://gscpap.com/integrations/amp)[

### Kiro

Add Google Search Console to Kiro as a remote MCP server. One entry in mcp.json, the token read from an approved environment variable, read-only access.

5 steps · 5 min read

](https://gscpap.com/integrations/kiro)[

### Raycast

Add Google Search Console to Raycast AI as an HTTP MCP server. Dynamic OAuth means no token to paste, and HTTP servers work on Raycast for iOS too.

5 steps · 4 min read

](https://gscpap.com/integrations/raycast)[

### GitHub Copilot CLI

Add Google Search Console to GitHub Copilot CLI with one command or one JSON entry. Remote HTTP transport, your token in a header, read-only access.

5 steps · 5 min read

](https://gscpap.com/integrations/copilot-cli)[

### n8n

Give an n8n AI Agent your Search Console data through the MCP Client Tool node, and schedule the SEO report you keep meaning to write.

6 steps · 6 min read

](https://gscpap.com/integrations/n8n)[

### LibreChat

Add GSC PAP to librechat.yaml as a streamable-http MCP server, and give every user on your install their own Search Console access rather than a shared one.

6 steps · 6 min read

](https://gscpap.com/integrations/librechat)

### Top tools to try first in Cursor

The MCP exposes 36 tools across 9 categories. These are the ones most relevant to this page:

-   [list_sites](https://gscpap.com/tools#list_sites) · List every Search Console property you have access to, with verification state and permission level.
-   [get_performance_overview](https://gscpap.com/tools#get_performance_overview) · High-level performance snapshot for a site: clicks, impressions, CTR, position over the last N days.
-   [find_quick_wins](https://gscpap.com/tools#find_quick_wins) · Find queries ranking positions 5 to 20 with at least 100 impressions but under 5% CTR: the title and snippet fixes most likely to lift clicks.
-   [search_analytics_query](https://gscpap.com/tools#search_analytics_query) · Run any Search Analytics query with full dimension and filter support, identical to what you'd hit the GSC API for, but inline in chat.

[Browse all 36 tools](https://gscpap.com/tools)

Done. Your AI client now has access to your Search Console data.

Got stuck? Email [support@gscpap.com](mailto:support@gscpap.com) with the error and we will revise the guide.
