--- title: "Search Console MCP for Google Antigravity · GSC PAP" source: https://gscpap.com/integrations/antigravity updated: 2026-10-19 --- [All integrations](https://gscpap.com/integrations) Integration · Google Antigravity # Connect Google Antigravity to Google Search Console 5 steps · about 5 minutes By the [GSC PAP team](https://gscpap.com/about) · Updated October 19, 2026 Google Antigravity is Google's agent-first development environment, and it speaks Model Context Protocol across all three of its surfaces: the App, the IDE and the CLI. Adding GSC PAP gives its agents read-only access to your Search Console, Google Analytics 4 and PageSpeed data. There is a pleasing circularity to this one. Google does not ship a Search Console MCP server, so the fastest way to ask Google's own editor about your Google search traffic is a hosted bridge to Google's own API. Antigravity performs dynamic client registration for OAuth-enabled servers, and GSC PAP implements it. So unlike most editors, this setup needs no token at all: you paste a URL, approve a consent screen, and Antigravity stores and refreshes the tokens itself. The bearer-token route still works if you prefer it, and both are below. ## How to connect Google Search Console to Antigravity 1. ### Sign in to GSC PAP once Go to gscpap.com, click "Sign in with Google" and approve the read-only access. Choose which of your properties to authorize. For the OAuth route in the next step you do not need to copy anything from this page; the authorization happens later, inside Antigravity. 2. ### Open your MCP server list In the Antigravity App, click Settings at the bottom left, then Customizations, and find the Installed MCP Servers section. Clicking Add MCP opens the MCP Store, a searchable list of ready-made servers. GSC PAP is not in that store, so add it as a custom server using the configuration in the next step. The IDE and the CLI read the same standardized format. 3. ### Add GSC PAP with OAuth, no token Every server lives under a single mcpServers object. A remote server is defined by serverUrl rather than command. With nothing else set, Antigravity discovers that the server supports OAuth, registers itself through dynamic client registration, and opens the GSC PAP consent screen the first time it connects. ```json { "mcpServers": { "gsc-pap": { "serverUrl": "https://mcp.gscpap.com/mcp" } } } ``` 4. ### Or use a bearer token instead If you would rather authenticate with a header, copy a token from app.gscpap.com/account/tokens and put it in the headers object. This is the right choice for a token scoped to a subset of your sites, for example on a client project. ```json { "mcpServers": { "gsc-pap": { "serverUrl": "https://mcp.gscpap.com/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } } ``` 5. ### Approve the tools, then ask By default any MCP tool Antigravity has not been told about runs in Ask mode, so the first call waits for your approval. Since nothing GSC PAP exposes can modify a property, allowing the whole server in your policy configuration is reasonable: mcp(gsc-pap/\*) matches all of its tools, and mcp(gsc-pap/list_sites) matches one. Then ask: "List my Search Console sites, then show the top 10 queries by clicks for the last 28 days." ```text mcp(gsc-pap/*) ``` ## Antigravity MCP setup: common issues - The key for a remote server is serverUrl, not url. A server entry needs either command for a local process or serverUrl for a remote one. - GSC PAP is not in the MCP Store, so Add MCP will not find it. Add it as a custom server with the JSON above. - With the OAuth route there is no token in your config at all. Antigravity keeps its access tokens in ~/.gemini/antigravity/mcp_oauth_tokens.json, refreshes them when they expire and removes invalid ones, and the server reconnects on its own after you authenticate. - authProviderType: "google_credentials" is for Google APIs that accept Application Default Credentials. It is not the setting for this server: GSC PAP has its own OAuth, so leave it out. - GSC PAP exposes 36 tools. If that is more than you want in the model's context, disabledTools takes a list of tool names to withhold. - Antigravity's own permissions system decides when a tool needs approval. A tool that silently never runs is usually waiting in Ask mode rather than failing to connect. ## Frequently asked questions ### Does Google Antigravity support remote MCP servers? Yes, on the App, the IDE and the CLI, with one standardized configuration format. A remote server is declared with serverUrl for Streamable HTTP or SSE, and it can carry custom headers, OAuth client credentials, or Google Application Default Credentials. ### Can I connect an MCP server to Antigravity without pasting a token? Yes, if the server supports OAuth with dynamic client registration, which GSC PAP does. Give Antigravity only the serverUrl and it registers itself, sends you through the consent screen, and manages the tokens from then on. Manual client credentials are only needed for servers without dynamic registration, and those use https://antigravity.google/oauth-callback as the redirect URI. ### Does Google have an official Search Console MCP server? Not as of October 2026. Google publishes MCP servers for several of its products, and Antigravity's MCP Store carries many of them, but Search Console is not among them. A hosted bridge such as GSC PAP covers it with read-only scopes, and the setup is one JSON entry. ### How do I stop Antigravity asking before every Search Console call? Allow the server in your permissions policy. mcp(gsc-pap/\*) matches every tool on the server, and a narrower mcp(gsc-pap/list_sites) matches one. Unconfigured MCP tools default to Ask mode, which is a sensible default for servers that can write, and unnecessary friction for a read-only one. ## 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)[ ### 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 Google Antigravity 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. - [inspect_url](https://gscpap.com/tools#inspect_url) · Single-URL deep dive: indexability, last crawl, canonical, mobile usability, structured data. The full URL Inspection API result. - [pagespeed_insights](https://gscpap.com/tools#pagespeed_insights) · Run a Google PageSpeed Insights (Lighthouse) audit. Returns performance / accessibility / best-practices / SEO scores, Core Web Vitals lab values (LCP, FCP, CLS, TBT), and the top opportunities ranked by potential savings. [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.