Support keyword: antigravity cli mcp
MCP is one of the first places Gemini CLI migrations can break. Check the Antigravity-specific config path, auth provider, and token file before blaming the server.
Updated on 2026-05-26. Independent guide. Use official Google links for downloads and account actions.
Searchers looking for antigravity cli mcp usually do not want a definition of Model Context Protocol. They want to know why a server that worked in Gemini CLI is missing, unauthenticated, or invisible after the Antigravity CLI migration. Google's docs describe Antigravity-specific MCP configuration rather than simply reusing the old Gemini CLI settings file shape.
The safe approach is to treat MCP migration as a small integration test: locate the new config file, add one server, verify auth, restart the CLI, and only then migrate the rest of your servers.
| Item | Location or setting | Use |
|---|---|---|
| MCP config | ~/.gemini/antigravity/mcp_config.json | Stores Antigravity MCP server configuration. |
| OAuth tokens | ~/.gemini/antigravity/mcp_oauth_tokens.json | Stores MCP OAuth token material generated through the auth flow. |
| Google credentials auth | authProviderType: "google_credentials" | Uses Google Application Default Credentials where supported. |
Do not paste secrets into a public issue or support form. If you need help, redact tokens, client secrets, workspace paths, and private server URLs.
mcp_config.json.The common mistake is copying an old Gemini CLI settings block into the wrong place. Antigravity and Antigravity CLI separate MCP configuration into their own file. If the server does not appear, check location, JSON validity, required environment variables, and auth provider before reinstalling the CLI.
A useful MCP support report should include the server name, whether it is local or remote, the auth provider type, the config file path you edited, whether the JSON validates, and whether the same server worked in Gemini CLI before migration. It should not include token values, private client secrets, or full internal URLs. If the issue only appears after migration, mention whether you used the official migration flow or copied settings by hand.
This information matters because MCP failures can look identical from the prompt: "tool not found", "server failed", or "auth required" may come from three different causes. A clean report lets you separate path problems, OAuth problems, and server runtime problems quickly.
Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.
Google's MCP docs describe ~/.gemini/antigravity/mcp_config.json as the Antigravity MCP configuration file.
Google's docs describe ~/.gemini/antigravity/mcp_oauth_tokens.json for MCP OAuth token storage.
No. Add one server, verify auth and visibility, then migrate the rest.