Install in Antigravity

Run surface

1. Send this to your agent

It reads the guide, registers the gateway and hands you the browser authorization — no key to copy.

Fetch and execute the appropriate instructions to connect Antigravity to Spinrun from https://docs.spinrun.ai/install/agents.md

In the IDE, open the agent panel's … menu → MCP Servers → Manage MCP Servers → View raw config. In Antigravity 2.0 it is Settings → Customizations → Installed MCP Servers; in the CLI, type /mcp. Add this server block to Antigravity's MCP configuration file, then restart it — or run spinrun install antigravity and let the CLI merge it for you.

{
  "mcpServers": {
    "spinrun": {
      "serverUrl": "https://spinrun.ai/mcp",
      "headers": {
        "x-spinrun-client": "antigravity"
      }
    }
  }
}

Fallback — If it asks for a key instead: If Antigravity asks for a credential instead of opening a browser, add a headers block with your key.

{
  "mcpServers": {
    "spinrun": {
      "serverUrl": "https://spinrun.ai/mcp",
      "headers": {
        "x-spinrun-key": "YOUR_API_KEY",
        "x-spinrun-client": "antigravity"
      }
    }
  }
}

3. Authorize in your browser

There is no key in that block on purpose. Antigravity opens a browser the first time it connects. Open Agent Settings (⌘,) → Customizations, click Authenticate next to spinrun, finish in the browser, then paste the authorization code it shows back into the panel and click Submit. Sign in and choose which workspace Antigravity may reach. You can revoke it any time from Settings → Applications.

4. Verify it can see your apps

Ask Antigravity to call spinrun_list_apps. Every app the workspace connects from now on appears there without reinstalling anything, and the client's page in the dashboard flips to Connected the moment the first call lands.

Build surface

1. Send this to your agent

This is the Build surface — it authors agents and workflows rather than running tools, and it accepts browser authorization only. The agent reads the guide, registers the endpoint and hands you the browser authorization — no key to copy.

Fetch and execute the appropriate instructions to connect Antigravity to the Spinrun Build endpoint from https://docs.spinrun.ai/install/agents.md

2. Edit the MCP config

This is the Build surface — it authors agents and workflows rather than running tools, and it accepts browser authorization only. In the IDE, open the agent panel's … menu → MCP Servers → Manage MCP Servers → View raw config. In Antigravity 2.0 it is Settings → Customizations → Installed MCP Servers; in the CLI, type /mcp. Add this server block to Antigravity's MCP configuration file, then restart it — or run spinrun install antigravity --build and let the CLI merge it for you.

{
  "mcpServers": {
    "spinrun-build": {
      "serverUrl": "https://spinrun.ai/mcp/build",
      "headers": {
        "x-spinrun-client": "antigravity"
      }
    }
  }
}

3. Authorize in your browser

There is no key in that block, and there is no key form of it. Antigravity opens a browser the first time it connects. Open Agent Settings (⌘,) → Customizations, click Authenticate next to spinrun, finish in the browser, then paste the authorization code it shows back into the panel and click Submit. Sign in and choose which workspace Antigravity may author in. Tick "Build authorization" on the consent screen, or enable it later under Settings → Applications (workspace owners only). You can revoke it any time from Settings → Applications.

4. Verify it can author

Ask Antigravity to call spinrun_build_options. A 403 naming insufficient_scope means the grant has no Build authorization yet: enable it under Settings → Applications, or revoke and authorize again with the box ticked. The client's page in the dashboard flips to Connected the moment the first call lands.

Notes

Only serverUrl is read — url and httpUrl are rejected.
A workspace-local .agents/mcp_config.json is read as well.
Tools default to Ask; allow mcp(spinrun/*) in the permissions to stop the prompts.
Some antigravity-cli builds drop the bearer token after authorizing; the key fallback covers that.

On this page