Keep Kiro.
Give it your machines.

AI Commander is not an alternative to Kiro, Claude Code, Codex, ChatGPT, Cursor, GitHub Copilot, Sourcegraph Cody, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, Amp, Kilo Code, OpenHands, Amazon Q Developer, Augment Code, Devin, or JetBrains Junie. 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: Junie · Cursor · GitHub Copilot · Cody · OpenHands · Amazon Q · Augment · Devin · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · goose · Amp · Kilo Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini · Cua Spaces · Warp.

Connect Kiro (remote MCP)

Kiro, the agentic IDE and CLI (Kiro MCP configuration docs), reads MCP servers from an mcp.json file. Per Kiro’s docs, remote servers are declared with a url (plus optional headers), and Kiro handles the browser-based OAuth flow for servers that use Dynamic Client Registration. Point it at AI Commander’s hosted MCP endpoint:

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

Use ~/.kiro/settings/mcp.json for user scope (all workspaces) or .kiro/settings/mcp.json in the workspace for project scope — if both exist, Kiro merges them and the workspace entry wins. In the IDE, open the command palette and run Kiro: Open user MCP config (JSON), or use the Open MCP Config icon in the Kiro panel; saving the file reconnects servers. Do not commit secrets: if you add an Authorization header with an API key, reference an environment variable (for example "Bearer ${AIC_API_KEY}") and approve it in Kiro’s Mcp Approved Env Vars setting.

Prefer a local stdio bridge?

{
  "mcpServers": {
    "aicommander": {
      "command": "npx",
      "args": ["-y", "@aicommander/mcp"],
      "env": { "AICOMMANDER_SERVER": "https://aicommander.dev" }
    }
  }
}

Keep tools behind Kiro’s approval prompt at first; only add AI Commander tools to autoApprove once you trust the workflow. You can also hide tools you do not want an agent to call with disabledTools.

Full client matrix (Kiro, Warp, Junie, Augment, Devin, Claude Code, Codex, ChatGPT, Cursor, Copilot, Cody, Grok, Gemini, OpenCode, Qwen Code, goose, Amp, Kilo Code, Continue, Windsurf, Cline, Roo Code, Zed, OpenHands, Amazon Q, 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. For optional account features (saved aliases), pass a Bearer API key in headers. Menu names and options can differ between Kiro versions — check the linked Kiro docs for your build.

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, test suites, and training on the box that has the repo.
• Fleet list + GPU facts so Kiro 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