--- title: "Google Search Console MCP for Zed Editor · GSC PAP" source: https://gscpap.com/integrations/zed updated: 2026-09-18 --- [All integrations](https://gscpap.com/integrations) Integration · Zed Editor # Connect Zed to Google Search Console 3 steps · about 4 minutes By the [GSC PAP team](https://gscpap.com/about) · Updated September 18, 2026 Zed is an open-source code editor with a built-in AI agent. It talks to Model Context Protocol (MCP) servers, which it lists under context_servers in its settings, and it can connect to remote servers over HTTP. GSC PAP plugs in as a remote server. You add a URL and one Authorization header; there is no extension to install. ## How to add Google Search Console to Zed 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 it asks for. The connect page then shows your bearer token once, so copy it now. If you lose it, create a new one at app.gscpap.com/account/tokens; your other tokens keep working. 2. ### Add gsc-pap as a remote MCP server Open Settings > AI > MCP Servers, click Add Server, and choose Add Remote Server. Zed writes what you enter to your settings file. To edit that file directly, run zed: open settings file from the command palette and add the entry below under context_servers, with your token in place of YOUR_TOKEN. If context_servers already exists, add only the gsc-pap entry. ```json { "context_servers": { "gsc-pap": { "url": "https://mcp.gscpap.com/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } } ``` 3. ### Check the status and ask a question Go back to Settings > AI > MCP Servers. The dot next to gsc-pap turns green, with the tooltip "Server is active", once Zed connects. Then open the Agent Panel and ask: "Use gsc-pap to list my Search Console sites." Naming the server helps the model pick its tools. By default, Zed asks for approval before it runs a tool. ## Zed context server troubleshooting - Put url and headers directly on the gsc-pap entry, as shown above. Zed's docs do not use a nested transport object for remote servers. - Keep the Authorization header. When a remote server has no Authorization header, Zed starts the MCP OAuth sign-in flow instead of sending a token. - If the dot is not green, hover over it to read the status, then run zed: open log from the command palette and look for lines that mention gsc-pap. - A "Missing or invalid bearer token" error means the token is wrong or was revoked. Create a new one at app.gscpap.com/account/tokens. ## Frequently asked questions ### Do I need a Zed extension to use Google Search Console? No. GSC PAP is a remote HTTP server, so you add it under context_servers in settings.json or through Add Remote Server. There is nothing to install and no local process to keep running. ### Is a Google Cloud project required to connect Zed to Search Console? No. GSC PAP is hosted and its Google OAuth client is already registered. Signing in with Google at gscpap.com gives you a bearer token, and that token is the only credential Zed needs to reach your Search Console data. ### Can Zed's assistant change my Search Console data? No. Access is read-only: GSC PAP holds the webmasters.readonly scope, so it can read sites, search analytics, sitemaps and URL inspection results, but it cannot write, modify, or delete anything. ## 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)[ ### 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)[ ### 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. 5 steps · 4 min read ](https://gscpap.com/integrations/warp)[ ### 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 Zed Editor 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. - [get_performance_overview](https://gscpap.com/tools#get_performance_overview) · High-level performance snapshot for a site: clicks, impressions, CTR, position over the last N days. - [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. - [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. [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.