Install Antigravity

Antigravity speaks remote Streamable HTTP MCP and connects to StateLode’s hosted endpoint directly — no bridge required. The default way in is Connect with StateLode: add the server by URL and sign in through your browser, with no token to mint, paste, or rotate. A static token is still available for headless and CI use further down. Like Windsurf, it uses serverUrl (not url) for remote servers. The IDE, CLI, and Antigravity 2.0 share one config file.

Config format verified against Antigravity’s MCP integration docs as of 2026-06. (Earlier guides routed Antigravity through statelode-bridge; it now connects over HTTP natively.)

Connect with StateLode (recommended)

Add the StateLode server without an Authorization header. When Antigravity connects it detects that the server needs authorization, opens your browser to sign in to StateLode (via WorkOS), and lets you pick a workspace; Antigravity then stores and refreshes the credential for you. Nothing to paste, nothing to rotate, and it survives restarts. Your role in that workspace sets access — owner, admin, and member get read + write; viewer is read-only.

Open the MCP store → Manage MCP Servers → View raw config, or edit the shared file directly at ~/.gemini/config/mcp_config.json, and add the server with just its serverUrl — no headers block:

{
  "mcpServers": {
    "statelode": {
      "serverUrl": "https://api.statelode.dev/mcp"
    }
  }
}

Back in the MCP store, Refresh; the statelode server will prompt you to sign in. Complete the browser consent and it lists three tools (task_search, task_get, task_mutate).

Static token (machine & CI)

Prefer Connect above for everyday use. Reach for a static statelode_live_… token when there is no browser for a consent flow — CI jobs, headless agents, or shared service accounts. Mint one in the dashboard and keep it out of git — see Token security. Don’t paste it into Antigravity’s agent chat to have it write the config for you. (You can ask the agent to open ~/.gemini/config/mcp_config.json so you paste the config and token in yourself — see Let the agent open the file.)

Add the token in an Authorization header. This file lives in your home directory, outside any repo — keep it that way, and chmod 600 ~/.gemini/config/mcp_config.json on a shared machine:

{
  "mcpServers": {
    "statelode": {
      "serverUrl": "https://api.statelode.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_STATELODE_TOKEN"
      }
    }
  }
}

Verify

Ask Antigravity:

Search StateLode for active tasks in project statelode.

On the first tool call, the hosted StateLode dashboard should show your latest activity, and Antigravity should return task_search results.

Troubleshooting

• statelode is waiting to sign in — that’s the Connect path. Complete the browser consent from the MCP store’s sign-in prompt, then Refresh.
• Error: calling "initialize": EOF — Antigravity expects a JSON-RPC response to the initialize POST. StateLode’s endpoint returns exactly that; if you see this, you’re pointed at a stale API build. Confirm the URL is https://api.statelode.dev/mcp and re-run Refresh in the MCP store.
• Used url instead of serverUrl — Antigravity ignores url for remote servers; the field must be serverUrl.
• 401 / no tools on the token path — re-check the Authorization header: Bearer then the token. Or drop the header and use Connect instead.