Antigravity Setup Guide

Antigravity is Google's agentic coding environment, available as an IDE, an app and a CLI. It supports the Model Context Protocol, so its agent can call Proxima's 41 tools. All Antigravity surfaces read the same mcp_config.json format, and its permission system asks you before an MCP tool runs unless you allow it.

Before you start: install Proxima, open the desktop app and log in to a provider (or add a BYOK key). The MCP entry point src/mcp/index.js forwards calls to the desktop app, so the app has to be running. Node.js 18 or newer must be on your PATH.

1. Register the Proxima MCP server

Antigravity keeps every MCP server definition in mcp_config.json. The simplest way to open it from the IDE is through the agent panel:

1 In the Agent panel, open the Additional Options menu (the three dots) and choose MCP Servers.
2 Choose Manage MCP Servers, then View raw config. This opens mcp_config.json in the editor. In the Antigravity App you can reach the same list through Settings, Customizations, Installed MCP Servers.
3 Add Proxima under mcpServers and save:
{ "mcpServers": { "proxima": { "command": "node", "args": [ "C:/path/to/proxima/src/mcp/index.js" ], "timeoutSeconds": 600 } } }

Use forward slashes on Windows. The optional timeoutSeconds raises the limit for a single tool call. Antigravity's default is three minutes per call and five minutes to connect, which is short for a slow reasoning model or a multi-model tool such as crew or run_loop. A positive value replaces both limits, so keep it large enough for the server to start.

Antigravity's own reference for the file and its properties (command, args, env, cwd, disabled, enabledTools, disabledTools) is on antigravity.google/docs/mcp.

Trimming the tool list

Each tool you expose costs the agent some context. If you only want part of Proxima, list the tools to keep with enabledTools, or hide some with disabledTools:

"proxima": { "command": "node", "args": ["C:/path/to/proxima/src/mcp/index.js"], "enabledTools": ["list_available_models", "ask_claude", "ask_gemini", "ask_perplexity", "deep_search", "ddg_search", "web_scrape", "smart_query", "analyze_file"] }

2. Verify the connection

1 Check that proxima appears in the MCP server list as connected, with its tools listed.
2 Ask the agent to call list_available_models. It should return the models your accounts offer. This proves Antigravity, the MCP process, the Proxima app and your logins all work together.
3 When Antigravity asks for approval, allow the call. To stop being asked for trusted tools, add a permission entry such as mcp(proxima/ddg_search) for one tool, or mcp(proxima/*) for the whole server, in your policy configuration.

3. Rules that steer the agent toward Proxima

Antigravity loads persistent rules from your workspace and combines them with any global rules. A short rule file can tell the agent when Proxima's tools are the right choice. Put it in one of these places:

  • AGENTS.md or GEMINI.md in the workspace root (plain Markdown, always active), or in any subfolder to scope it to that folder.
  • .agents/rules/*.md for several smaller rules. Each file starts with YAML frontmatter that sets a trigger (always_on, model_decision, glob or manual).
  • Global rules for every project: ~/.gemini/AGENTS.md or ~/.gemini/GEMINI.md.

Example AGENTS.md:

# Using Proxima tools - For questions about current library versions or recent changes, call the proxima `deep_search` tool (type "web" or "github") before answering from memory. - To read a specific page, use proxima `web_scrape`. To find pages first, use `ddg_search`. - Before relying on a model name, call proxima `list_available_models` and use a name it returns. - To cross-check an important answer, call proxima `smart_query` with mode "verify". - After changing code, use proxima `review_code_file` on the changed file.

Keep each rule file under 24 KB. Antigravity truncates larger files and limits the total size of always-on rules, so concise rules work best.

4. Troubleshooting

  • The server does not connect. Validate the JSON in mcp_config.json, use forward slashes, and run node --version to confirm Node 18+. A wrong path to index.js is the most common cause.
  • A tool call times out. Raise timeoutSeconds as shown above, and try a faster model with list_available_models.
  • Tool calls fail but the server is connected. Open the Proxima app and sign in to the provider again. ddg_search works without a provider and helps you tell the two cases apart.

See the troubleshooting guide for more, and What's new in 5.5.0 for the model-discovery changes.