Connect Antigravity

Reaching Manage MCP Servers in Antigravity

From the chat window’s additional-options menu choose Manage MCP Servers, then View Raw Config. Paste the JSON below, save, and hit Refresh on the Manage MCP Servers page (or restart Antigravity).

The raw config JSON, using serverUrl

{
  "mcpServers": {
    "zopnight": {
      "serverUrl": "MCP_SERVER_URL",
      "headers": {
        "Authorization": "Bearer MCP_PAT"
      }
    }
  }
}

The Server URL comes from your Organisation Settings page; the token is your own zn_pat_… personal access token.

Refresh is not optional

Antigravity does not hot-reload the MCP config. After saving, press Refresh on the Manage MCP Servers page, or restart the app. A config that is correct but unrefreshed looks exactly like a config that is wrong, which makes this worth checking first.

Note the key name: serverUrl, matching Windsurf rather than Cursor.

What the read-only tier gives Antigravity

At the default org setting, read-only, 85 of the 119 tools work immediately. That covers cost totals by team or tag, spend trends, budget health, detected anomalies, the full resource inventory, recommendations with their savings, Kubernetes logs and events, and deploy history.

Ask for a cost overview first; it is the entry point the tool set is designed around.

Write tiers, seen from Antigravity

Mutating tools sit behind an org-level dial with four positions, each cumulative:

Your own RBAC still applies on top: the tier is a ceiling, not a bypass. Roles, user management, credentials and cloud-account deletion are never reachable at any tier.

Antigravity shows no tools after Refresh

Two causes account for almost every case. Either MCP is not enabled for the organisation, or the transport is wrong. MCP is off by default, and an admin turns it on in Organisation Settings. Every mutating call is audit-logged with its source, so MCP activity stays distinguishable from UI and API activity afterwards.