Integration · Claude Code
Connect Claude Code to Google Search Console
3 steps · about 3 minutes
By the GSC PAP team · Updated
GSC PAP is a hosted Google Search Console MCP server, so connecting it to Claude Code takes one claude mcp add command with your token. There is no Google Cloud project to create, no Search Console API to enable, no OAuth credentials to download, and no local Python server to keep running.
Claude Code is Anthropic's CLI agent for terminal-based work. It runs in any directory, has full access to your file system, and supports MCP servers natively. Unlike Claude Desktop and Cursor where you edit a JSON file by hand, Claude Code uses a single CLI command to register a server.
User-scope (--scope user) means GSC PAP becomes available in every project where you run Claude Code - no per-repo configuration needed. Avoid --scope project for this server: it writes the command, including your bearer token, into .mcp.json, a file meant to be committed to git.
This guide assumes Claude Code is installed (npm install -g @anthropic-ai/claude-code) and you are signed in.
How to add the Search Console MCP server to Claude Code
- 1
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. The connect page shows your one-time bearer token. Copy it. The next step needs it inside a CLI command.
- 2
Run claude mcp add
In any terminal, run the command below. Replace YOUR_TOKEN with the bearer from step 1. The --scope user flag makes the server available globally and keeps your token in your own user config, out of the repo.
shellclaude mcp add --transport http --scope user gsc-pap https://mcp.gscpap.com/mcp \ --header "Authorization: Bearer YOUR_TOKEN" - 3
Verify and use
Type claude inside any directory to start an interactive session. Run /mcp inside the chat to see registered servers - gsc-pap should be listed with its tools. Then ask: "List my Search Console sites and show top 5 queries on each from last week." Claude Code chains the tool calls automatically.
Managing and troubleshooting the server in Claude Code
- ·Run claude mcp list to see what is registered. Run claude mcp remove gsc-pap to delete the server (you can re-add later with a new token).
- ·If /mcp says "failed to reconnect," the most common cause is the MCP server having restarted in the meantime. Just retry - GSC PAP runs in stateless mode so reconnects are instant.
- ·The --scope user config lives in ~/.claude.json. You can edit it manually if needed, but the CLI is safer.
- ·Claude Code's terminal mode disables some color sequences. If JSON output looks scrambled, redirect to a file: claude > out.txt and read it after.
Frequently asked questions
Do I need a Google Cloud project or API key for Claude Code?
No. You sign in with Google at gscpap.com and copy a bearer token. GSC PAP calls the Search Console API with its own registered OAuth client, so you never create a project, enable the API, or handle a client secret JSON file.
Should I use --scope user, local or project?
Use --scope user to have Search Console in every repo; Claude Code stores it in ~/.claude.json, private to you. To limit it to one repo, use local scope (the default), which is also private. Project scope writes the server, including your bearer token, to .mcp.json in the repo root, a file meant to be committed. If you use it, change the header in .mcp.json to Bearer ${GSC_PAP_TOKEN} and set that environment variable; Claude Code expands it.
Can Claude Code change my Search Console settings?
No. GSC PAP requests the read-only webmasters.readonly scope. Claude Code 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 GSC PAP 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.
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.
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.
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.