Keep Amazon Q Developer.
Give it your machines.

AI Commander is not an alternative to Amazon Q Developer, Claude Code, Codex, ChatGPT, Cursor, GitHub Copilot, Sourcegraph Cody, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, Amp, or Kilo Code. 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: Amazon Q Developer stays the brain; AI Commander is the hands on the box — servers, GPU rigs, NAS, laptops — with no inbound ports and no exposed SSH.

Sibling harness pages: Cursor · GitHub Copilot · Cody · OpenHands · Augment · Devin · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · goose · Amp · Kilo Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect Amazon Q Developer (MCP HTTP)

Amazon Q Developer (MCP docs) supports remote MCP servers over HTTP in the CLI / Q Chat, and MCP in the IDE chat. Point it at AI Commander’s hosted MCP endpoint:

Amazon Q agent config — remote HTTP
{
  "mcpServers": {
    "aicommander": {
      "type": "http",
      "url": "https://aicommander.dev/mcp"
    }
  }
}

CLI / Q Chat: add or edit the remote server in your Amazon Q agent configuration (qchat mcp add for managed entries; remote HTTP uses type + url as above). After connect, run /mcp in the CLI if OAuth is required and follow the browser URL. IDE: Amazon Q Chat → Configure MCP servers → add an HTTP server named aicommander with URL https://aicommander.dev/mcp (global ~/.aws/amazonq/ or workspace .amazonq/). Prefer a local stdio bridge?

stdio bridge
$ npx -y @aicommander/mcp

Wire that command under mcpServers.aicommander with command/args (and optional env AICOMMANDER_SERVER=https://aicommander.dev) in ~/.aws/amazonq/mcp.json or your agent default.json — same pattern as other stdio MCP clients.

Full client matrix (Amazon Q, Claude Code, Codex, ChatGPT, Cursor, Copilot, Cody, Grok, Gemini, OpenCode, Qwen Code, goose, Amp, Kilo Code, Continue, Windsurf, Cline, Roo Code, Zed, REST): Connect your AI client. Amazon Q MCP docs: Using MCP with Amazon Q Developer · CLI MCP config · IDE MCP config.

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 header where your Amazon Q build supports it.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
Amazon Q Developertype: http → https://aicommander.dev/mcp (or npx -y @aicommander/mcp)
OpenHandsopenhands mcp add aicommander --transport http https://aicommander.dev/mcp
Ampamp mcp add aicommander https://aicommander.dev/mcp
goosegoose session --with-streamable-http-extension "https://aicommander.dev/mcp"
Kilo Codemcp.aicommander.url → 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
Copilot / CodyHTTP MCP / cody.mcpServers + bridge
Cline / Roo Code / ZedMCP settings / context_servers + bridge or remote URL

How Amazon Q Developer handles MCP servers

Checked against AWS docs: MCP configuration for Amazon Q Developer CLI and AWS: Amazon Q Developer IDE plugins end of support in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits Amazon Q Developer

Many Q users already work in AWS all day. AI Commander covers what Q can't reach: machines outside AWS, such as an on-prem build server, a lab GPU box or a NAS.

  1. Add aicommander as an HTTP server in the Q CLI agent config and complete the /mcp sign-in.
  2. Ask Q to compare a deployment: query the AWS side with its usual tools, then run remote_exec on the on-prem box to check the same service version and config.
  3. For a long sync or build, have Q start it with remote_job_start and check remote_job_status before you close the session.

Limits and gotchas in Amazon Q Developer

FAQ

Is AI Commander an alternative to Amazon Q Developer?
No. AI Commander is a remote-machine harness. You keep Amazon Q Developer (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) as the AI. 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 Amazon Q Developer to AI Commander?
Add AI Commander as a remote MCP server for Amazon Q. CLI / Q Chat: configure a remote HTTP server with type http and url https://aicommander.dev/mcp in your Amazon Q agent config (or use qchat mcp add for a stdio bridge with npx -y @aicommander/mcp). IDE: Amazon Q Chat → Configure MCP servers → add HTTP transport pointing at https://aicommander.dev/mcp, or edit ~/.aws/amazonq/mcp.json (legacy) / agent default.json under mcpServers. 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 Amazon Q running locally only?
Local Amazon Q Developer is the brain in your IDE chat or Q CLI. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Amazon Q can run shell, detached jobs, and file transfer on those machines over MCP.
What happens to my AI Commander setup when the Amazon Q IDE plugins reach end of support?
Nothing breaks on the AI Commander side. AWS points IDE users to Kiro. Copy the aicommander entry into .kiro/settings/mcp.json or ~/.kiro/settings/mcp.json and check its fields against Kiro's MCP configuration page.
Why does Amazon Q CLI say aicommander is not loaded?
If the server needs OAuth, Q shows it as not loaded until you sign in. Run /mcp, open the URL it prints and sign in.
Should a new AI Commander setup go into Amazon Q or Kiro?
For editor use, Kiro, because AWS has announced end of support for the Amazon Q Developer IDE plugins on April 30, 2027. Moving later means copying the aicommander entry and checking its fields against Kiro's format.
How do I pass a comma inside --args to qchat mcp add?
Escape the comma, or give --args as a JSON array. Without that, Q splits the value into two arguments.

Next steps

Install the agent on a machine you control, connect Amazon Q Developer via remote HTTP MCP (or npx -y @aicommander/mcp), then ask for a real task on a remote box.