--- title: "Google Search Console MCP Server for Warp · GSC PAP" source: https://gscpap.com/integrations/warp updated: 2026-10-19 --- [All integrations](https://gscpap.com/integrations) Integration · Warp # Connect Warp to Google Search Console 5 steps · about 4 minutes By the [GSC PAP team](https://gscpap.com/about) · Updated October 19, 2026 Warp is a terminal with an agent built into it, and that agent can call Model Context Protocol tools. Adding GSC PAP gives it read-only access to your Search Console, Google Analytics 4 and PageSpeed data, in the same window where you build and deploy the site. Warp adds MCP servers through its own UI rather than a config file you edit by hand, so this is mostly clicking, with one JSON block to paste. GSC PAP is hosted, which means you add it as a URL-based server. There is no local process, no Google Cloud project and no credentials file. ## How to connect Google Search Console to Warp 1. ### Sign in to GSC PAP and copy your token Go to gscpap.com and click "Sign in with Google." Approve the read-only access, choose which sites to grant, and copy the bearer token shown on the connect page. It is shown once; you can create more at app.gscpap.com/account/tokens. 2. ### Open Warp's MCP servers panel Go to Settings, then Agents, then MCP servers. You can also reach the same list from Warp Drive, under Personal, then MCP Servers. Both open the place where Warp keeps its servers. 3. ### Add a URL-based server Click + Add and pick the "Streamable HTTP or SSE Server (URL)" type. Warp asks for JSON rather than separate fields. 4. ### Paste the server definition Paste the block below, replacing YOUR_TOKEN with the token from step 1. Warp's shape is a bare object keyed by the server name: there is no mcpServers wrapper here, unlike Claude Desktop or Cursor. ```json { "gsc-pap": { "url": "https://mcp.gscpap.com/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } ``` 5. ### Press Start, then ask something Warp does not start a newly added server by itself, so click Start on the gsc-pap entry. Once it is running, ask the agent: "List my Search Console sites, then show the top queries by clicks for the last 28 days." If you deploy from this terminal, the follow-up worth asking is whether the pages you just shipped are indexed. ## Warp MCP setup: common issues - A newly added server stays stopped until you click Start. A server that looks added but answers nothing is usually just not started. - Do not wrap the JSON in mcpServers. Warp expects the server name as the top-level key. - Pick the URL server type, not the command type. GSC PAP is hosted, so there is no command for Warp to run. - "Missing or invalid bearer token" means the token is wrong or was revoked. Create a new one at app.gscpap.com/account/tokens and edit the entry. ## Frequently asked questions ### Does Warp support remote MCP servers? Yes. Warp connects to remote or locally hosted MCP endpoints over Streamable HTTP or SSE, and it can send custom request headers, which is how a bearer token reaches the server. ### Where do I add an MCP server in Warp? Settings, then Agents, then MCP servers, or from Warp Drive under Personal, then MCP Servers. Click + Add, choose the Streamable HTTP or SSE Server (URL) type, paste the server JSON, then click Start. ### Can Warp's agent change my Search Console property? Not through GSC PAP. It only requests read-only Google scopes, so no tool it exposes can edit a property, submit a sitemap or remove a URL, however the agent is prompted. ## Other integrations [All integrations](https://gscpap.com/integrations) [ ### Claude Desktop Connect Claude Desktop to Google Search Console without creating a Google Cloud project. Sign in with Google, paste one config block, restart Claude. 6 steps · 6 min read ](https://gscpap.com/integrations/claude-desktop)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/cursor)[ ### 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. 3 steps · 3 min read ](https://gscpap.com/integrations/claude-code)[ ### 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. 4 steps · 4 min read ](https://gscpap.com/integrations/codex-cli)[ ### 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. 4 steps · 4 min read ](https://gscpap.com/integrations/vscode-copilot)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/gemini-cli)[ ### 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. 4 steps · 5 min read ](https://gscpap.com/integrations/windsurf)[ ### 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. 3 steps · 4 min read ](https://gscpap.com/integrations/zed)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/jetbrains)[ ### 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. 4 steps · 4 min read ](https://gscpap.com/integrations/continue)[ ### 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. 3 steps · 3 min read ](https://gscpap.com/integrations/claude-ai-connectors)[ ### 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. 4 steps · 5 min read ](https://gscpap.com/integrations/mcp-direct)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/opencode)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/cline)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/lm-studio)[ ### 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. 5 steps · 6 min read ](https://gscpap.com/integrations/chatgpt)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/goose)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/antigravity)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/roo-code)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/kilo-code)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/amp)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/kiro)[ ### 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. 5 steps · 4 min read ](https://gscpap.com/integrations/raycast)[ ### 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. 5 steps · 5 min read ](https://gscpap.com/integrations/copilot-cli)[ ### 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. 6 steps · 6 min read ](https://gscpap.com/integrations/n8n)[ ### 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. 6 steps · 6 min read ](https://gscpap.com/integrations/librechat) ### Top tools to try first in Warp The MCP exposes 36 tools across 9 categories. These are the ones most relevant to this page: - [list_sites](https://gscpap.com/tools#list_sites) · List every Search Console property you have access to, with verification state and permission level. - [search_analytics_query](https://gscpap.com/tools#search_analytics_query) · Run any Search Analytics query with full dimension and filter support, identical to what you'd hit the GSC API for, but inline in chat. - [batch_inspect_urls](https://gscpap.com/tools#batch_inspect_urls) · Bulk URL Inspection, up to 10 URLs per call within Google's 2,000-per-day quota. Diagnose why a content cluster or sitemap isn't getting indexed. - [get_index_coverage_summary](https://gscpap.com/tools#get_index_coverage_summary) · Get an account-wide breakdown of indexing states (indexed, crawled-not-indexed, discovered-not-indexed) so you know where to focus. - [find_quick_wins](https://gscpap.com/tools#find_quick_wins) · Find queries ranking positions 5 to 20 with at least 100 impressions but under 5% CTR: the title and snippet fixes most likely to lift clicks. [Browse all 36 tools](https://gscpap.com/tools) Done. Your AI client now has access to your Search Console data. Got stuck? Email [support@gscpap.com](mailto:support@gscpap.com) with the error and we will revise the guide.