Integrate Unleash with Google Gemini and Antigravity

The Unleash MCP server connects Google’s agentic coding tools to your Unleash instance, enabling AI-assisted feature flag management. This page covers how to install and configure the server in Antigravity and Gemini. To learn what the server can do, see Unleash MCP server.

Google’s current agentic platform is Antigravity, the successor to Gemini CLI. It supports MCP across two local surfaces that share one engine and configuration:

• Antigravity desktop app — The flagship “agent control tower,” where you launch and supervise many agents in parallel
• Antigravity CLI — The same engine in the terminal, run with the agy command

If your team is still on Gemini Code Assist or Gemini CLI under a paid license, that setup remains supported. See Gemini Code Assist and Gemini CLI below.

Prerequisites

Before you begin, make sure you have the following:

• Node.js 24 or later: The MCP server is distributed as an npm package
• Antigravity: The desktop app or the CLI)
• A signed-in Antigravity session: Sign in with your Google account, or use Cloud OAuth against a Gemini Enterprise Agent Platform project for enterprise
• An Unleash instance: Cloud or self-hosted, with API access enabled
• A personal access token (PAT): With permissions to create and manage feature flags

Install the MCP server

Antigravity stores MCP configuration in a dedicated mcp_config.json file. The desktop app and the CLI read the same configuration, so you set up the server once.

mkdir -p ~/.unleash
cat > ~/.unleash/mcp.env << 'EOF'
UNLEASH_BASE_URL=https://your-instance.getunleash.io
UNLEASH_PAT=your-personal-access-token
EOF
chmod 600 ~/.unleash/mcp.env

# Unleash MCP credentials
if [ -f ~/.unleash/mcp.env ]; then
  source ~/.unleash/mcp.env
  export UNLEASH_BASE_URL UNLEASH_PAT
fi

{
  "mcpServers": {
    "unleash": {
      "command": "npx",
      "args": ["-y", "@unleash/mcp@latest"],
      "env": {
        "UNLEASH_BASE_URL": "${UNLEASH_BASE_URL}",
        "UNLEASH_PAT": "${UNLEASH_PAT}"
      }
    }
  }
}

/mcp

Approval and oversight model

Antigravity enforces an authoring-time boundary that also governs how MCP tool calls run. The controls differ slightly between the two surfaces.

In the CLI

The CLI gates agent actions through permission modes. Documented values include always-proceed, agent-decides, and asks-for-review, with stricter modes like request-review and strict. Useful flags:

• --mode sets the execution mode for the session (either accept-edits or plan)
• --sandbox runs with terminal restrictions
• --dangerously-skip-permissions auto-approves every tool request (reserve for isolated environments)

Keep a prompting mode for writes so you review the flag name, environment, or rollout before a write like release or kill_switch runs.

In the desktop app

The desktop app applies the same gate through a Human-in-the-Loop review pane. As an agent works, it produces Artifacts (plans, task lists, walkthroughs, and browser recordings) that you review and comment on inline before it proceeds.

Desktop review can be relaxed to proceed automatically, which is convenient but removes the human gate. Treat local review as an authoring-time convenience, and rely on the feature flag (and, at enterprise scale, Cloud IAM) as the boundary that cannot be switched off. Enable change requests on production environments so enabling a flag requires human approval regardless of what any agent does.

Tools and workflows

Once the server is connected, Antigravity and Gemini can use every tool the Unleash MCP server exposes. To learn what the server can do and see step-by-step workflows, read Unleash MCP server. For the current list of tools, see the README on GitHub.

Feedback reports

To opt in to feedback reports, set UNLEASH_MCP_SEND_FEEDBACK to "true" in the env block of ~/.gemini/config/mcp_config.json. For Gemini CLI and Gemini Code Assist, set it in ~/.gemini/settings.json. Antigravity and Gemini CLI don’t show consent prompts, so feedback reports stay off until you set the variable. To learn more, see Clients without a consent prompt.

To hide the send_feedback tool from the assistant, set the variable to "false". To learn what a report contains, see What is recorded.

Enterprise governance

Enterprises run Antigravity through the Gemini Enterprise Agent Platform. Developers connect the desktop app and the CLI to a Google Cloud project with Cloud OAuth and an Agent Platform Project ID and region. Agent inference then runs inside your own cloud boundary, with regional endpoints and Google Cloud’s standard data protections.

MCP tool use is governed by Google Cloud IAM, so you enforce the approved path centrally rather than per machine:

• Grant access deliberately — The roles/mcp.toolUser role controls who and what can call MCP tools.
• Allowlist tools — IAM Deny policies on mcp.googleapis.com/tools.call let you permit the vetted Unleash tools and block others, filtered by tool name, read-only status, service, or OAuth client.
• Secure the deployment — Agent Identity, Agent Gateway, Agent Security, and Agent Registry govern how agents authenticate and connect.

This pairs with Unleash’s own governance. The MCP server inherits the PAT’s permissions and cannot exceed them, so scope the token tightly. Enable change requests on production so enabling a flag requires human approval regardless of what any agent requests. Antigravity governs how the agent runs and which tools it can reach; Unleash governs how the release ships.

Managed agents and the remote server

Antigravity can run managed agents server-side, each in its own isolated, network-restricted sandbox. Those sandboxes cannot reach a local stdio server, so for flag operations inside a managed agent, use the remote Unleash MCP server with the serverUrl field:

{
  "mcpServers": {
    "unleash-remote": {
      "serverUrl": "https://your-instance.getunleash.io/api/admin/mcp",
      "headers": { "Authorization": "${UNLEASH_PAT}" }
    }
  }
}

Your Unleash instance exposes this endpoint at /api/admin/mcp once you enable it under Admin settings > Remote MCP server. Pass your PAT as the raw Authorization header value, with no Bearer prefix. Antigravity uses serverUrl for remote servers (Gemini CLI used url). Make the host reachable, allow write methods, and verify the authentication flow works in a headless environment. For everyday work in the desktop app and CLI, the local stdio server is simpler.

Gemini Code Assist and Gemini CLI

The move from Gemini CLI to Antigravity is a transition, not a hard cutover. On June 18, 2026, Gemini CLI and the Gemini Code Assist IDE extensions stopped serving the free, Google AI Pro, and Ultra tiers, and Gemini Code Assist for GitHub stopped accepting new installations. Access under a paid Gemini Code Assist Standard or Enterprise license remains unchanged, so those teams can keep using Gemini CLI and Code Assist today.

In that setup, configure the Unleash MCP server in ~/.gemini/settings.json under a mcpServers key (Gemini CLI supports both $VAR and ${VAR} expansion there):

{
  "mcpServers": {
    "unleash": {
      "command": "npx",
      "args": ["-y", "@unleash/mcp@latest"],
      "env": {
        "UNLEASH_BASE_URL": "${UNLEASH_BASE_URL}",
        "UNLEASH_PAT": "${UNLEASH_PAT}"
      }
    }
  }
}

When you move to Antigravity, the MCP configuration moves to mcp_config.json, and you can bring your existing setup across with agy plugin import gemini. The Unleash tools and workflows are identical on both.

Troubleshooting

Related resources

• Unleash MCP server on GitHub
• Google Antigravity documentation
• Antigravity MCP configuration
• Antigravity hooks
• Gemini Enterprise Agent Platform
• Impact Metrics
• Unleash architecture overview