Keep Gemini.
Give it your machines.

AI Commander is not an alternative to Gemini, ChatGPT, Claude Code, Cursor, Grok, or Codex. It is the remote-machine harness those tools plug into over MCP: outbound-only shell, detached jobs that outlive the chat, and file transfer on hardware you already own.

Sibling harness pages: Claude Code · Cursor · Grok · Codex · ChatGPT · Roo Code · Zed · OpenCode · Qwen Code · Continue.

Connect Gemini CLI (HTTP MCP)

Gemini CLI talks to AI Commander over remote Streamable HTTP MCP. One command — pass --transport http and use user scope so it lands in ~/.gemini/settings.json:

Prefer a local stdio bridge? One command (or put the same block under mcpServers in ~/.gemini/settings.json):

Or set httpUrl / command+args under mcpServers.aicommander in ~/.gemini/settings.json. Use httpUrl (not legacy SSE url) for Streamable HTTP. Full client matrix (Gemini, Codex, ChatGPT, Claude Code, Cursor, Grok, REST): Connect your AI client.

First connect may open a one-time browser sign-in (OAuth Dynamic Client Registration). For a code-only first hour without that flow, append ?anonymous=1 to the MCP URL where your client supports it.

MCP stack for Gemini CLI

AI Commander is one of three MCP servers we add to Gemini CLI. The other two are MCPfinder (MCP server discovery) and cnvs.app (a shared whiteboard). The exact gemini mcp add commands, what each server adds and what to check before you add it are on one page: MCP stack for Gemini CLI. The same stack for other clients, plus PLAI.chat for second opinions from other models: Agent stack.

Antigravity CLI (agy)

Google’s Antigravity CLI keeps MCP servers in its own file, not in Gemini CLI’s settings.json: ~/.gemini/config/mcp_config.json for all projects, or .agents/mcp_config.json in one project. Remote servers need serverUrl (url and httpUrl are not supported there). Since 1.1.16, agy mcp add writes the user-level file for you (Antigravity MCP docs, 1.1.16 release notes, checked 2026-10-19):

Pick one of the two. Flags such as --env go before the server name; an https:// URL is detected as HTTP automatically (checked against agy mcp add --help in 1.4.2). Then run agy mcp list, or /mcp inside the CLI, to check the server and its tools. Editing the file by hand instead, the HTTP entry is:

{
  "mcpServers": {
    "aicommander": {
      "serverUrl": "https://aicommander.dev/mcp"
    }
  }
}

What you get that the chat alone cannot

• Remote shell on Linux, macOS, and Windows — by session code or saved alias.
• Detached jobs for builds, training, and headless agents on the box that has the repo.
• Fleet list + GPU facts so Gemini picks the right machine before it burns an hour.
• File courier (Pro) for checkpoints and diffs up to 100 MiB.

Not a replacement — a multiplier

FAQ