All integrations

Integration · Claude Desktop

Add GSC PAP to Claude Desktop

5 steps · about 5 minutes

Claude Desktop is Anthropic's official desktop app for Claude. It supports the Model Context Protocol (MCP) over HTTP, which means external tools - like your Search Console data via GSC PAP - can be plugged in through a single JSON config file.

This guide walks through every step from a fresh Claude Desktop install to your first search analytics query. No GCP project, no client_id JSON, no command line beyond pasting one config block. About five minutes end-to-end.

If you already have Claude Desktop installed, skip step 1.

Steps

  1. 1

    Install Claude Desktop

    Download Claude Desktop from claude.ai/download. The installer is signed and notarized for macOS, signed for Windows. Open the app and sign in with your Anthropic account. You do not need a paid Claude plan to use MCP servers - the Free tier works.

  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 scope. After the OAuth callback, the connect page shows a one-time bearer token. Click "Copy token" - the next step needs it. If you lose it, mint a new one from /account/tokens; existing tokens stay valid.

  3. 3

    Find your Claude Desktop config file

    Claude Desktop stores its MCP server config in a single JSON file. The path depends on your OS - it does not exist by default; create it if missing.

    shell
    # macOS
    ~/Library/Application Support/Claude/claude_desktop_config.json
    
    # Windows
    %APPDATA%\Claude\claude_desktop_config.json
    
    # Linux (Claude Desktop is currently macOS/Windows only)
  4. 4

    Add the GSC PAP server block

    Open the config file in any text editor (TextEdit, Notepad, VS Code). Paste the block below. Replace YOUR_TOKEN with the bearer you copied in step 2. If the file already has other MCP servers, add gsc-pap as a new key inside mcpServers - do not overwrite the whole block.

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

    Restart Claude Desktop and ask a question

    Quit Claude Desktop completely (Cmd+Q on macOS, right-click in tray on Windows) and reopen. The MCP server initializes during startup - takes a few seconds. Open a new chat and ask: "What sites are in my Search Console?" Claude calls list_sites and replies with your verified properties. From there: "Show me my top queries last week."

Common gotchas

  • ·Token expired or 401 errors: mint a new bearer at /account/tokens. Old tokens stay valid unless you revoke them - so you can rotate without breaking other clients.
  • ·Claude Desktop says "server failed to start": check that the JSON config has no trailing commas or unmatched braces. JSON is strict about syntax. Run the file through jq or jsonlint if unsure.
  • ·Tools list is empty: confirm the URL is exactly https://mcp.gscpap.com/mcp (with /mcp suffix). Without /mcp the request hits the wrong endpoint and silently fails.
  • ·On Windows, %APPDATA% expands to C:\Users\<you>\AppData\Roaming. The Claude folder is usually hidden - enable "Show hidden files" in File Explorer.

Other integrations

All integrations

Cursor

Use Search Console data inside Cursor's AI chat. Five-step setup, single JSON config, works in any project.

5 steps · 5 min read

Claude Code

Two-line CLI setup for Claude Code, Anthropic's terminal-based agent. User-scope means it works in every project automatically.

3 steps · 3 min read

Codex CLI (OpenAI)

Connect Google Search Console, GA4, and PageSpeed Insights to OpenAI's Codex CLI in three minutes. Bearer-token auth via env var, works in both the CLI and the Codex IDE extension.

4 steps · 4 min read

VS Code (GitHub Copilot)

Wire your Google Search Console + GA4 + PageSpeed data into VS Code's GitHub Copilot agent mode in five minutes. Native MCP support since VS Code 1.101.

5 steps · 5 min read

Gemini CLI (Google)

Connect Search Console, GA4, and PageSpeed data to Google's Gemini CLI agent. Streamable HTTP MCP support, bearer-token auth, works inside Gemini's 1M-token context window.

4 steps · 4 min read

Windsurf IDE

Plug Search Console, GA4, and PageSpeed data into Windsurf's Cascade agent in five minutes. Bearer-token auth, works with both local and remote agent runs.

4 steps · 5 min read

Zed Editor

Wire Search Console, GA4, and PageSpeed Insights into Zed's AI assistant. Native MCP context-server support via settings.json.

3 steps · 4 min read

JetBrains IDEs

Wire Search Console, GA4, and PageSpeed into IntelliJ, PyCharm, WebStorm, GoLand, any JetBrains IDE 2025.2 or newer. Native MCP support via the AI Assistant settings.

4 steps · 5 min read

Continue (extension)

Continue is a popular open-source AI coding assistant with VS Code and JetBrains extensions. Add GSC PAP as an MCP server in three minutes via its config.json.

3 steps · 3 min read

Claude.ai (browser)

Connect Search Console, GA4, and PageSpeed to Claude.ai in your browser through the Connectors panel. OAuth flow, no token to copy, no config file to edit. Works for free and paid Claude plans.

3 steps · 3 min read

Direct HTTP (curl, custom agents)

GSC PAP speaks Streamable HTTP MCP. Any client that can POST JSON-RPC over HTTP with a bearer Authorization header can use it, curl, Python scripts, custom LangChain agents, even shell aliases.

3 steps · 4 min read

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

Got stuck? Email support@gscpap.com with the error and we will revise the guide.