--- title: "Continue MCP: Add Google Search Console · GSC PAP" source: https://gscpap.com/integrations/continue updated: 2026-09-18 --- [All integrations](https://gscpap.com/integrations) Integration · Continue (extension) # Connect Continue to Google Search Console 4 steps · about 4 minutes By the [GSC PAP team](https://gscpap.com/about) · Updated September 18, 2026 Continue is an open-source AI coding assistant for VS Code and JetBrains IDEs. It reads MCP servers from the mcpServers list in its config.yaml and uses their tools in Agent mode. If Continue is already installed and set up with a model, this takes about four minutes. ## How to add Google Search Console to Continue 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. ### Save the token as a Continue secret Continue's IDE extensions cannot read environment variables from your shell, so store the token in Continue's global .env file. Create ~/.continue/.env (on Windows, %USERPROFILE%\\.continue\\.env) with the line below, using your token with no quotes around it. Keep this file out of version control. ```shell GSC_PAP_TOKEN=YOUR_TOKEN ``` 3. ### Add gsc-pap to config.yaml Open the Continue sidebar (Cmd/Ctrl+L in VS Code, Cmd/Ctrl+J in JetBrains), click the config selector above the chat input, and click the gear icon next to your local config. That opens ~/.continue/config.yaml. Add the gsc-pap item under mcpServers; if the file already has an mcpServers list, add only the item. Save the file and Continue reloads the config on its own. ```yaml mcpServers: - name: gsc-pap type: streamable-http url: https://mcp.gscpap.com/mcp requestOptions: headers: Authorization: Bearer ${{ secrets.GSC_PAP_TOKEN }} ``` 4. ### Ask in Agent mode Continue only uses MCP tools in Agent mode. Switch the chat to Agent and ask: "List my Search Console sites." Continue calls list_sites from gsc-pap and shows your verified properties. ## Continue MCP config: common issues - The older config.json format is deprecated. When config.yaml exists, Continue loads it instead of config.json, so add the server to config.yaml. - "unresolved secrets: GSC_PAP_TOKEN" means Continue could not find the secret. Check that ~/.continue/.env exists and that the name matches exactly. Continue also looks in .env and .continue/.env at the workspace root. - Instead of requestOptions.headers, you can write apiKey: ${{ secrets.GSC_PAP_TOKEN }} on the server entry. Continue sends apiKey as an Authorization: Bearer header. - 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 and update ~/.continue/.env. ## Frequently asked questions ### Does this work in both the VS Code and JetBrains versions of Continue? Yes. Both read the same ~/.continue/config.yaml and ~/.continue/.env, so the steps are identical. Continue reloads the config when you save it. ### Does the same setup work in the Continue CLI? Yes. The Continue CLI (cn) accepts the same mcpServers entry. Unlike the IDE extensions, the CLI can also read GSC_PAP_TOKEN from your shell environment. ### Do I need a Google Cloud project to add Search Console to Continue? No. GSC PAP runs the Google side for you, so there is no project to create, no Search Console API to enable, and no credentials file to manage. The only thing you give Continue is the bearer token from gscpap.com. ### Is GSC PAP free? Yes. It is free during the public preview, with no credit card and no feature gate. Usage limits are 60 MCP tool calls per minute and 1,000 per hour per user. ## 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)[ ### 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 Continue (extension) 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.