Integration · Claude.ai (browser)
Add GSC PAP to Claude.ai via Connectors
3 steps · about 3 minutes
Claude.ai is Anthropic's browser-based Claude, the one most users start with before installing the desktop app or Claude Code. As of 2025 it supports remote MCP servers through the Customize → Connectors panel, with full OAuth 2.0 + Dynamic Client Registration handling.
GSC PAP exposes a fully-conformant OAuth 2.0 + DCR provider (RFC 7591), which means Claude.ai can register itself as a client, redirect you through the consent flow, and persist a refresh token, all without you ever touching a config file or copying a bearer.
This is the lowest-friction integration we offer: three clicks, no tokens, no config.
Steps
- 1
Open Claude.ai → Customize → Connectors
Go to claude.ai, click your avatar (bottom-left) → Customize → Connectors. The panel lists already-installed connectors and has an "Add custom connector" button at the top.
- 2
Add the GSC PAP MCP URL
Click "Add custom connector" and paste the MCP URL. Leave the auth method on OAuth (Claude.ai will discover the OAuth metadata automatically via /.well-known/oauth-authorization-server). Click Connect.
texthttps://mcp.gscpap.com/mcp - 3
Approve the OAuth consent screen
Claude.ai redirects you to gscpap.com's consent page (showing what scope it's requesting on your behalf). Click "Authorise." You land back in Claude.ai with the connector active. Now ask any chat: "What sites are in my Search Console?". Claude calls list_sites and returns your verified properties.
Common gotchas
- ·The first time, Claude.ai also walks you through Google sign-in (gscpap.com → Sign in with Google) if you haven't done that before. Subsequent connector additions skip that step.
- ·Custom connectors are available on all Claude plans (free and paid). If your Customize menu lacks the Connectors entry, your Claude.ai workspace may have it disabled by an admin, switch to your personal account.
- ·Tokens issued via OAuth are revocable from app.gscpap.com/account/tokens just like manually-minted ones. They show as "Sign-in" source in the dashboard.
- ·If GSC PAP rolls into the official Connectors directory (Anthropic's curated list), the install becomes a single click, no need to paste the URL. Until then the custom-connector flow is the path.
Other integrations
All integrationsClaude 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.
Cursor
Use Search Console data inside Cursor's AI chat. Five-step setup, single JSON config, works in any project.
Claude Code
Two-line CLI setup for Claude Code, Anthropic's terminal-based agent. User-scope means it works in every project automatically.
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.
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.
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.
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.
Zed Editor
Wire Search Console, GA4, and PageSpeed Insights into Zed's AI assistant. Native MCP context-server support via settings.json.
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.
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.
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.