2.6 Antigravity CLI | Installation

Installation is similar on Linux, macOS, and Windows (with WSL2 enabled on Windows).

Antigravity CLI loads global MCP servers from `~/.gemini/config/mcp_config.json`. Do not add them to `~/.gemini/antigravity-cli/settings.json`; that file stores CLI preferences and the MCP screen can still show `No MCP servers configured`.

This applies to Antigravity CLI.

Local configuration:

Validate the package first, then add the same MCP entry to `~/.gemini/config/mcp_config.json`.

npx -y @luminondev/mcp-dashboard mcp

If that command starts without errors, create or update `~/.gemini/config/mcp_config.json` with this configuration:

{
  "mcpServers": {
    "luminon": {
      "command": "npx",
      "args": ["-y", "@luminondev/mcp-dashboard", "mcp"]
    }
  }
}

Remote configuration:

Luminon exposes the server over HTTP. Start it with `luminon start remote`.

luminon start remote

If your client version supports remote MCP servers by URL, add the following:

{
  "mcpServers": {
    "luminon_remote": {
      "url": "<myluminonserver>",
      "headers": {
        "Authorization": "Bearer <lbt_token>"
      }
    }
  }
}

The `Authorization` Bearer token is generated with `luminon token create`, as explained in 2.3 . The URL is the IP address or domain name of the machine where Luminon is running. With the `luminon_remote` name, you can keep this connection alongside `luminon` for the local MCP in the same `settings.json`.