Integration · Gemini CLI (Google)
Add GSC PAP to Google's Gemini CLI
4 steps · about 4 minutes
Gemini CLI is Google's terminal coding agent. It supports Model Context Protocol servers natively, with a 1M-token context that lets you feed in entire GSC reports without truncation.
Setup mirrors the other CLI agents: install, copy a token from gscpap.com, register the server in the Gemini config, restart.
Steps
- 1
Install Gemini CLI
Follow the install instructions at https://github.com/google-gemini/gemini-cli (or `npm install -g @google/gemini-cli` if available for your version). Sign in with `gemini auth login` using your Google account.
- 2
Sign in to GSC PAP and copy your token
Visit gscpap.com → Sign in with Google → grant the Search Console + GA4 scopes → copy the bearer token shown on the connect page.
- 3
Add gsc-pap to your Gemini settings
Edit `~/.gemini/settings.json` (path may vary across versions; check the Gemini CLI docs for `mcp_servers` config location). Register the gsc-pap server with the URL and Authorization header.
json{ "mcp_servers": { "gsc-pap": { "url": "https://mcp.gscpap.com/mcp", "transport": "http", "headers": { "Authorization": "Bearer YOUR_TOKEN_HERE" } } } } - 4
Restart Gemini CLI and test
Quit any open Gemini session and reopen. Ask: "List my Google Search Console sites and pull the top 5 queries from last week." Gemini calls list_sites then search_analytics_query and returns the answer in chat.
Common gotchas
- ·Gemini CLI's MCP config path/format varies between releases. If the example above doesn't work for your version, run `gemini mcp --help` and check the official docs at https://github.com/google-gemini/gemini-cli for the current syntax.
- ·Bearer tokens with environment-variable substitution may be supported in newer versions, prefer that over inline pasting if available.
- ·If you hit `gsc-pap` connection errors, verify the URL is exactly https://mcp.gscpap.com/mcp (with /mcp suffix). Without /mcp the request hits the wrong endpoint and silently fails.
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.
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.
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.
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.