You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: Antigravity guide points at a config file path that does not exist #3839
docs/installation-guides/install-antigravity.md instructs users to edit ~/.gemini/antigravity/mcp_config.json. That file is not where Antigravity stores MCP configuration, and on a current install it does not exist at all. Antigravity's global MCP configuration is ~/.gemini/config/mcp_config.json.
The guide also states that Antigravity uses serverUrl "instead of url" for HTTP-based MCP servers. Antigravity accepts both keys, so that wording sends readers looking for a limitation that does not exist.
Evidence
Antigravity's own documentation describes the configuration locations as:
On a current Antigravity install (macOS, build from 2026-11-02) the file that exists is ~/.gemini/config/mcp_config.json. The ~/.gemini/antigravity/ directory holds only the generated per-server tool caches (~/.gemini/antigravity/mcp/<serverName>/<toolName>.json), not the configuration.
The same path and key rules appear in the agent guide that ships inside the Antigravity language server, which describes url as the key for Streamable HTTP and serverUrl as the accepted legacy alias.
Impact
A reader who follows the guide either edits a file Antigravity never reads, or creates one and still sees no server appear. The troubleshooting section compounds this by quoting the error message "Error: serverUrl or command must be specified", which does not appear in current Antigravity builds.
Suggested fix
Update docs/installation-guides/install-antigravity.md to:
point at ~/.gemini/config/mcp_config.json (C:\Users\<USERNAME>\.gemini\config\mcp_config.json on Windows);
state that both serverUrl and url are accepted for remote servers;
link to the Antigravity MCP documentation for the full schema;
replace the stale troubleshooting entry with a check that the URL points at the Streamable HTTP endpoint and that the config file is the global one.
Activity