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.

Quick start:
  1. Install the host agent on the machine you want your AI to control. It shows a private machine code.
  2. Connect your AI: paste this prompt, then replace AIC-… with your code — Help me connect this AI client to AI Commander using https://aicommander.dev/start.md. Then check the status of my machine: AIC-… — or add the connector URL https://aicommander.dev/mcp and sign in with an email code (per-client steps).
Positioning in one line: Kiro stays your spec-driven agentic IDE and CLI; AI Commander is the hands on the box — servers, GPU rigs, NAS, laptops — with no inbound ports and no exposed SSH.

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:

~/.kiro/settings/mcp.json — remote MCP
{
  "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?

mcp.json — 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.

Over the remote URL, first connect may open a one-time browser sign-in (OAuth Dynamic Client Registration). The npx bridge does not sign in through a browser: without AICOMMANDER_TOKEN in its env it connects anonymously with a code-only first hour; set it to your API key to bind it to your account. On the remote URL, append ?anonymous=1 to skip the sign-in, for a code-only first hour. 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

Not a replacement — a multiplier

You already useAI Commander adds
KiromcpServers.aicommander.url → https://aicommander.dev/mcp in ~/.kiro/settings/mcp.json
WarpSettings → Agents → MCP servers → + Add → https://aicommander.dev/mcp
JetBrains JuniemcpServers.aicommander.url in ~/.junie/mcp/mcp.json
Augment Codeauggie mcp add aicommander --transport http --url https://aicommander.dev/mcp
DevinSettings → MCP → custom HTTP → https://aicommander.dev/mcp
Claude Codeclaude mcp add --transport http … → remote exec + jobs
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec
Cursor / Continue / Windsurfnpx @aicommander/mcp stdio bridge

How Kiro handles MCP servers

Checked against Kiro docs: MCP configuration in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits Kiro

Kiro is spec-driven: it writes requirements and a task list before coding. AI Commander lets the tasks that need real hardware run on it.

  1. Add aicommander to the workspace .kiro/settings/mcp.json with autoApprove for list_machines, session_status and remote_job_status.
  2. In the spec, write the verification task plainly, for example "run the load test on the staging box as a background job and record p95 latency".
  3. When Kiro reaches that task it calls remote_job_start, then reads remote_job_logs and writes the numbers back into the task notes.

Limits and gotchas in Kiro

FAQ

Is AI Commander an alternative to Kiro?
No. AI Commander is a remote-machine harness. You keep Kiro (or 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) as the AI coding agent. AI Commander gives those tools secure remote shell, detached jobs, and file transfer on machines you own — over MCP or REST.
How do I connect Kiro to AI Commander?
Add AI Commander as a remote MCP server in Kiro's mcp.json: user scope ~/.kiro/settings/mcp.json or workspace scope .kiro/settings/mcp.json, with mcpServers.aicommander.url set to https://aicommander.dev/mcp. In the IDE, run Kiro: Open user MCP config (JSON) from the command palette. Prefer stdio? Use command npx with args -y @aicommander/mcp. The remote URL may ask for a one-time browser sign-in (OAuth); the npx bridge never does: it connects anonymously unless AICOMMANDER_TOKEN is set in its env. On the remote URL, use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.
How is this different from Kiro working in my workspace?
Kiro works on the workspace you have open in the IDE or terminal. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Kiro can run shell, detached jobs, and file transfer on those machines over MCP.
Why doesn't Kiro substitute my ${AICOMMANDER_KEY} variable?
Kiro only expands environment variables you have approved. Add the name to the Mcp Approved Env Vars setting, then save mcp.json again.
Do I need to restart Kiro after editing mcp.json?
No. Saving the file reloads it, and only the servers whose entries changed are restarted.

Next steps

Install the agent on a machine you control, add AI Commander to Kiro’s mcp.json (remote URL or npx -y @aicommander/mcp), then ask Kiro for a real task on a remote box.