Integration · Claude.ai (browser)
Add a Google Search Console connector to Claude.ai
3 steps · about 3 minutes
By the GSC PAP team · Updated
GSC PAP works as a Google Search Console (GSC) connector for Claude.ai. You paste its MCP URL into Claude's custom connector dialog, approve access, and Claude can read your Search Console, GA4 and PageSpeed data in the browser. You do not need a Google Cloud project, API credentials, or anything installed on your machine.
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.
How to add the Search Console connector in Claude.ai
- 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.
Things to know about the Claude.ai connector
- ·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.
Frequently asked questions
Which Claude plans can add a custom connector?
Anthropic offers custom connectors on Free, Pro, Max, Team and Enterprise plans, and limits Free users to one custom connector. On Team and Enterprise plans, an Owner adds connectors in Organization settings and members connect to them from Customize > Connectors.
Do I need a Google Cloud project or API key?
No. The connector signs you in with Google through GSC PAP's own OAuth client, which is already registered with Google. You never create a Google Cloud project, enable the Search Console API, or download credentials.
Can the connector change anything in Search Console?
No. GSC PAP requests the read-only webmasters.readonly scope. Claude can read your verified sites, search analytics, sitemap status and URL inspection results, but it cannot add or remove sites, submit sitemaps, or request indexing.
Is the GSC PAP connector free?
Yes, during the public preview. There is no credit card, no trial expiration and no feature gate. Each user can make 60 tool calls per minute and 1,000 per hour.
Other integrations
All integrationsClaude Desktop
Connect Claude Desktop to Google Search Console without creating a Google Cloud project. Sign in with Google, paste one config block, restart Claude.
Cursor
Connect Google Search Console to Cursor through a hosted MCP server. Sign in with Google, paste one token into mcp.json, and skip the Google Cloud project.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.