--- title: "Google Search Console MCP Server for Amp · GSC PAP" source: https://gscpap.com/integrations/amp updated: 2026-10-19 --- [All integrations](https://gscpap.com/integrations) Integration · Amp # Connect Amp to Google Search Console 5 steps · about 5 minutes By the [GSC PAP team](https://gscpap.com/about) · Updated October 19, 2026 Amp is Sourcegraph's coding agent, available in the editor and as a CLI, and it reads Model Context Protocol servers from its settings. Point it at GSC PAP and it can read your Search Console, Google Analytics 4 and PageSpeed data while it works in the repository those pages come from. GSC PAP is hosted, so the entry is a URL and a header. There is no local process and no Google Cloud project. Amp has three ways in: the settings file, one CLI command, or a remote definition stored on ampcode.com that keeps the token in a file rather than in settings. All three are below. ## How to connect Google Search Console to Amp 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. Choose which sites to authorize and copy the bearer token the connect page shows once. Further tokens, each limited to a subset of your sites, are at app.gscpap.com/account/tokens. 2. ### Put the token in your environment Amp expands ${VAR_NAME} inside header values, so the token does not have to live in a settings file you might sync or commit. ```shell echo 'export GSC_PAP_TOKEN="paste-your-token-here"' >> ~/.zshrc source ~/.zshrc ``` 3. ### Add the server to Amp's settings User settings live in ~/.config/amp/settings.json and workspace settings in .amp/settings.json. The key is amp.mcpServers, written with the dotted prefix inside the JSON object. ```json { "amp.mcpServers": { "gsc-pap": { "url": "https://mcp.gscpap.com/mcp", "headers": { "Authorization": "Bearer ${GSC_PAP_TOKEN}" } } } } ``` 4. ### Or add it from the CLI The CLI writes the entry for you. It has no flag for a header, so add the headers block to settings afterwards, or use the remote form in the gotchas below, which keeps the bearer token in a file of its own. ```shell amp mcp add gsc-pap https://mcp.gscpap.com/mcp ``` 5. ### Approve it if it came from the workspace, then ask A server defined in .amp/settings.json needs approval before it runs: amp mcp approve gsc-pap. Then ask Amp "list my Search Console sites, then show the top 10 queries by clicks for the last 28 days". The first call is list_sites, since every other tool needs the exact property URL. ```shell amp mcp approve gsc-pap ``` ## Amp MCP setup: common issues - The settings key is amp.mcpServers, with the prefix as part of the key name. A bare mcpServers object will not be read. - Workspace servers are not trusted automatically. Until amp mcp approve runs, the server is configured and inert. - The CLI cannot attach a header. For a token-authenticated server, either edit settings after amp mcp add, or use the remote definition form: amp mcp remote add GscPap https://mcp.gscpap.com/mcp --auth bearer --bearer-token-file /path/to/token --personal - A url entry is treated as local configuration even when the server is on another machine, which is only a naming quirk, not a limitation. - "Missing or invalid bearer token" usually means the environment variable was empty when Amp started. Check it in the shell you launch Amp from. ## Frequently asked questions ### Does Amp support remote MCP servers? Yes. A server entry with a url is a remote server, and a headers object carries authentication such as a bearer token. ${VAR_NAME} in a header value expands from the environment. ### Where does Amp keep its MCP configuration? Under the amp.mcpServers key, in ~/.config/amp/settings.json for your user or .amp/settings.json for a workspace. Workspace entries require amp mcp approve before they run. ### Can I add a Search Console MCP server to Amp from the command line? Yes: amp mcp add gsc-pap https://mcp.gscpap.com/mcp. The command does not take a header, so add the Authorization header to settings afterwards, or use amp mcp remote add with --auth bearer and --bearer-token-file to keep the token in a separate file. ## 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)[ ### 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 Amp 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. - [find_cannibalization](https://gscpap.com/tools#find_cannibalization) · Detect keyword cannibalization where multiple URLs compete for the same query, splitting click-through and confusing Google. - [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. [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.