--- title: "Google Search Console MCP Server for Kiro · GSC PAP" source: https://gscpap.com/integrations/kiro updated: 2026-10-19 --- [All integrations](https://gscpap.com/integrations) Integration · Kiro # Connect Kiro to Google Search Console 5 steps · about 5 minutes By the [GSC PAP team](https://gscpap.com/about) · Updated October 19, 2026 Kiro is AWS's agentic IDE, and it loads Model Context Protocol servers from an mcp.json it keeps per workspace and per user. GSC PAP is hosted, so it goes in as a remote server: an HTTPS URL plus an Authorization header. Once connected, Kiro's agent can read your Search Console clicks, impressions, CTR and average position, your GA4 numbers and PageSpeed field data, with read-only Google scopes and no Google Cloud project of your own. Kiro has one habit worth knowing before you start: it only expands environment variables in a config after you have explicitly approved them. That is the step people miss. ## How to connect Google Search Console to Kiro 1. ### Sign in to GSC PAP and copy your token Go to gscpap.com, click "Sign in with Google" and approve the read-only access. Pick the properties you want to expose, then copy the bearer token shown once on the connect page. You can create more, scoped to fewer sites, at app.gscpap.com/account/tokens. 2. ### Put the token in your environment Keeping it out of mcp.json matters here, because the workspace file is the one that tends to end up in a repository. ```shell echo 'export GSC_PAP_TOKEN="paste-your-token-here"' >> ~/.zshrc source ~/.zshrc ``` 3. ### Open the right mcp.json A workspace config lives at .kiro/settings/mcp.json and a user-level one at ~/.kiro/settings/mcp.json. If both exist Kiro merges them, and the workspace file takes precedence. For a token that should follow you across projects, use the user-level file. ```shell # workspace .kiro/settings/mcp.json # user, all workspaces ~/.kiro/settings/mcp.json ``` 4. ### Add the GSC PAP server Paste the entry below. Saving the file reconnects the server, so there is nothing to restart. ```json { "mcpServers": { "gsc-pap": { "url": "https://mcp.gscpap.com/mcp", "headers": { "Authorization": "Bearer ${GSC_PAP_TOKEN}" } } } } ``` 5. ### Approve the variable, then ask If Kiro warns about the variable instead of expanding it, add GSC_PAP_TOKEN to the "Mcp Approved Env Vars" setting. Then ask: "List my Search Console sites, then show me the queries ranking between 5 and 20 with a CTR under 2%." ## Kiro MCP setup: common issues - Kiro expands only environment variables you have approved. An unexpanded ${GSC_PAP_TOKEN} reaching the server looks exactly like a bad token, so check "Mcp Approved Env Vars" first. - The url has to be HTTPS. Plain HTTP is only allowed for localhost, which does not apply to a hosted server. - Workspace settings win over user settings when both define gsc-pap. If a change to the user file does nothing, look for .kiro/settings/mcp.json in the project. - Saving mcp.json reconnects the server by itself. If a tool list looks stale, save the file again rather than restarting the IDE. - Keep the token in the environment, not in a workspace mcp.json that a repository will carry. ## Frequently asked questions ### Does Kiro support remote MCP servers? Yes. A server entry with an HTTPS url is a remote server, and the headers object is passed to the server during connection, which is how a bearer token gets there. Plain HTTP is accepted only for localhost. ### Where is Kiro's MCP config file? .kiro/settings/mcp.json for a workspace and ~/.kiro/settings/mcp.json for your user. When both exist they are merged, with the workspace file taking precedence. ### Why is my environment variable not working in Kiro's mcp.json? Kiro expands only approved variables. Add the variable's name to the "Mcp Approved Env Vars" setting, then save mcp.json again. Until then the literal ${VAR} is sent, which the server rejects as an invalid token. ## 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)[ ### 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)[ ### 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 Kiro 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. - [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. - [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. - [pagespeed_field_data](https://gscpap.com/tools#pagespeed_field_data) · Pull real-user Core Web Vitals from the Chrome User Experience Report (CrUX). LCP, INP, CLS at the 75th percentile, plus FAST/AVERAGE/SLOW rating, for both URL and origin level. [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.