Setup
How do I add GSC PAP to Claude Desktop, Cursor, or Claude Code?
By the GSC PAP team · Updated
The flow is the same for all three clients: sign in with Google at gscpap.com, copy the bearer token shown on the connect screen, then paste a JSON config or run a single CLI command in your AI client. Total time about 60 seconds, all from the same web page.
For Claude Code, run a single claude mcp add command; the connect screen generates it with your token already filled in. For Cursor, add a url and headers entry to ~/.cursor/mcp.json. Claude Desktop is different: its config file only accepts servers it starts as a local command, so the connect screen gives you a claude_desktop_config.json that runs the mcp-remote bridge through npx (Node.js required). Put it at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows, then restart the app. Each client has a step-by-step guide under Integrations.
If you ever lose the token, you can mint a new one anytime from /account/tokens. Existing tokens stay valid (multi-bearer model), so you can rotate without breaking other clients. To revoke a specific token without affecting others, click revoke next to it in the same page - the rest keep working.
Related questions
All questionsSetup
Which AI clients support GSC PAP?
GSC PAP is exposed as an MCP (Model Context Protocol) server. Any AI client that speaks MCP can connect. We have setup guides for Claude Desktop, Cursor, Claude Code (the Anthropic CLI), Claude.ai Connectors, OpenAI Codex CLI, VS Code with GitHub Copilot, Gemini CLI, Windsurf, Zed, JetBrains AI Assistant and Continue, plus direct HTTP for custom agents. See /integrations for each one.
Setup
Do I need a Google Cloud project to use GSC PAP?
No. The whole reason GSC PAP exists is to remove the Google Cloud setup step. When you sign in with Google through gscpap.com, you grant permission to our OAuth client (which we registered with Google one time). We then call the Search Console API on your behalf using your refresh token. You never touch the Google Cloud Console.
Privacy & Security
Can other users see my data?
No. Your Search Console data, OAuth tokens, MCP sessions, archive, and tool call history are all isolated to your user account in our database. Every query passes through bearer-token authentication that resolves to a specific user, and every database query scopes results by user_id. There is no UI, API endpoint, or feature that exposes one user's data to another user.
Your Search Console data, in chat, in 60 seconds Stop CSV-exporting GSC data. Sign in with Google to ask in chat.
Sign in with Google