Keep Grok.
Give it your machines.

AI Commander is not an alternative to Grok, Claude Code, Codex, Cursor, or ChatGPT. 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.

Positioning in one line: Grok 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: Claude Code · Cursor · Grok · Codex · ChatGPT.

Connect Grok (HTTP MCP)

Grok Build / the grok CLI talks to AI Commander over remote HTTP MCP. One command:

grok CLI

$ grok mcp add --transport http aicommander https://aicommander.dev/mcp

Prefer a local stdio bridge? Or declare it in ~/.grok/config.toml:

~/.grok/config.toml

[mcp_servers.aicommander]
url = "https://aicommander.dev/mcp"

Stdio alternative: grok mcp add aicommander -- npx -y @aicommander/mcp with AICOMMANDER_SERVER=https://aicommander.dev. Full client matrix (Grok, Claude Code, Codex, ChatGPT, Cursor, 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.

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 Grok 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

You already use	AI Commander adds
Grok / `grok` CLI / grok build	`grok mcp add --transport http …` → remote exec + jobs
Cursor	`npx @aicommander/mcp` stdio bridge → remote exec + jobs
Claude Code	MCP remote exec + jobs on your fleet
Codex	Same MCP endpoint; aliases after sign-in
ChatGPT	Custom MCP connector or plain REST `/api/v1/exec`

FAQ

Is AI Commander an alternative to Grok?

No. AI Commander is a remote-machine harness. You keep Grok (or Claude Code, Codex, Cursor, ChatGPT) 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 Grok to AI Commander?

Run: grok mcp add --transport http aicommander https://aicommander.dev/mcp — then install the agent on the target machine and ask Grok to use the machine code or saved alias. Prefer a local stdio bridge? Use grok mcp add aicommander -- npx -y @aicommander/mcp with AICOMMANDER_SERVER=https://aicommander.dev. First connect may open a one-time browser sign-in (OAuth). Use ?anonymous=1 for a code-only first hour.

How is this different from Grok running locally only?

Local Grok is the brain on your laptop. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Grok can run shell, detached jobs, and file transfer on those machines over MCP.

Next steps

Install the agent on a machine you control, connect Grok via grok mcp add, then ask for a real task on a remote box.

Install the agent Setup guides Remote coding agents

Keep Grok.Give it your machines.