DecisionOps Documentation
IDE & MCP

Connect From Antigravity

Use this guide when you want to connect DecisionOps from Antigravity. Like Codex, Antigravity is modeled as a user-scoped MCP integration, but the config path is environment-driven instead of fixed to a single well-known file.

Use this guide when you want to connect DecisionOps from Antigravity. Like Codex, Antigravity is modeled as a user-scoped MCP integration, but the config path is environment-driven instead of fixed to a single well-known file.

What You Need First

Make sure you have:

  • Antigravity installed
  • access to the DecisionOps organization and project you want to use
  • the resolved value of ANTIGRAVITY_MCP_CONFIG_PATH

The current default DecisionOps MCP values for Antigravity are:

  • server name: decision-ops-mcp
  • server URL: https://api.aidecisionops.com/mcp

Find And Update The Config File

Open /integrations/agents in the dashboard and choose Antigravity. Select the organization, project, and repository context you want to install, then copy the generated setup details.

Next, find the actual MCP config file path by resolving ANTIGRAVITY_MCP_CONFIG_PATH in your local environment. Update that file to include the DecisionOps server entry. Because the path is environment-specific, this is the place where most setup confusion happens. If Antigravity is already configured elsewhere on the machine, verify that you are editing the file the app is really reading.

Run The First Tool Call

Once the config is saved, invoke any DecisionOps MCP tool from Antigravity. The first request should trigger the interactive OAuth handoff. Complete the DecisionOps sign-in and consent flow in the browser, then return to Antigravity and rerun the same tool call.

Confirm The Grant

Open /integrations/agents and verify that Antigravity now appears in the connected client list. If the grant is visible there, the integration is ready to use for the normal IDE workflow.

Troubleshooting

If Antigravity still cannot find the server, resolve ANTIGRAVITY_MCP_CONFIG_PATH again and confirm that you edited the right file. If consent completed but the tool still uses stale settings, restart Antigravity or reload its MCP settings so it picks up the updated server definition. If the connection succeeds but uses the wrong workspace context, regenerate the install details from the dashboard and update the stored values.

On this page