All integrations

Integration · JetBrains IDEs

Add GSC PAP to JetBrains AI Assistant

4 steps · about 5 minutes

JetBrains IDEs starting with version 2025.2 ship with built-in MCP support inside the AI Assistant. You add servers through Settings → Tools → AI Assistant → Model Context Protocol.

This guide works for IntelliJ IDEA, PyCharm, WebStorm, GoLand, RubyMine, PhpStorm, the AI Assistant settings panel is the same across the family.

Steps

  1. 1

    Verify your IDE version

    Help → About. You need 2025.2 or later. The MCP panel is hidden in earlier versions even if AI Assistant is installed.

  2. 2

    Sign in to GSC PAP and copy your token

    Visit gscpap.com → Sign in with Google → grant Search Console + GA4 scopes → copy the bearer token from the connect page.

  3. 3

    Open MCP settings and add gsc-pap

    Settings (Cmd/Ctrl + ,) → Tools → AI Assistant → Model Context Protocol → "+". Choose Streamable HTTP / Remote. Fill in name (`gsc-pap`), URL, and the Authorization header.

    json
    {
      "name": "gsc-pap",
      "transport": "http",
      "url": "https://mcp.gscpap.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  4. 4

    Verify connection and ask a question

    Click "Test connection". JetBrains pings the MCP and returns the tool count. Save. Open AI Assistant chat and ask: "What sites are in my Search Console? Give me the top 5 queries by clicks last week." The Assistant routes through gsc-pap.

Common gotchas

  • ·If "Test connection" returns 401, your token is invalid or has been revoked. Mint a new one at /account/tokens.
  • ·JetBrains stores the bearer in the IDE password safe (encrypted, OS keychain backing), safe for shared workstations but not exported when you sync settings across machines.
  • ·Some plugins conflict with AI Assistant's MCP host. If you can't add a server, disable competing AI plugins (other Copilot-like extensions) and restart.

Other integrations

All integrations

Claude Desktop

Wire your Google Search Console to Claude Desktop in five minutes. Step-by-step instructions for macOS and Windows, with the exact JSON config to paste.

5 steps · 5 min read

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

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.