Keep Msty Studio.
Give your models your machines.

AI Commander is not an alternative to Msty Studio, Claude Code, Codex, ChatGPT, or any other AI client. 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: Jan · Chatbox · LM Studio · AnythingLLM · TypingMind · Open WebUI · Claude Code · Codex · Claude Desktop — and the rest on Connect your AI client.

Connect Msty Studio (Toolbox, Streamable HTTP)

Msty Studio implements MCP in its Toolbox: local servers over STDIO / JSON and remote servers over Streamable HTTP (Msty Studio docs: Toolbox tools). Add AI Commander’s hosted endpoint as a remote tool:

1. Open the Toolbox and click Add New Tool.
2. Choose HTTP and enter the MCP server URL https://aicommander.dev/mcp.
3. Add the header Authorization: Bearer <your-api-key> (or see below for the no-account URL), give the tool a name and save it.
4. Add the tool to a toolset and select that toolset in your chat (Msty Studio docs: Toolsets).

URL:     https://aicommander.dev/mcp
Header:  Authorization: Bearer <your-api-key>

Create an API key in the AI Commander dashboard (see Accounts & API keys) and send it as the Authorization: Bearer header so the agent can list your machines and reach them by alias. No account yet? Use https://aicommander.dev/mcp?anonymous=1 as the URL instead (no header) for a code-only first hour, reaching machines by their AIC-… session code.

Prefer a local process? Choose STDIO / JSON instead and paste the stdio bridge (needs Node.js 20 or later; drop the env block if you have no key — the bridge then connects anonymously):

{
  "command": "npx",
  "args": ["-y", "@aicommander/mcp"],
  "env": {
    "AICOMMANDER_TOKEN": "<your-api-key>"
  }
}

Get the details right

• Transport: Msty Studio connects to remote servers over Streamable HTTP (not SSE), which is what https://aicommander.dev/mcp serves.
• Long work: start detached jobs (remote_job_start, then remote_job_status / remote_job_logs) instead of one long tool call.
• Models: pick a model with solid tool calling; the tools are the same whichever model you chat with.

By default, API keys and OAuth connectors only act while the account owner has opened the AI Commander dashboard in the last 24 hours (accounts can disable that gate under Credential security) — see Connect your AI client. AI Commander’s endpoint is first-party and only acts on machines where you installed the agent yourself. Menus and options can differ between Msty Studio versions — check the linked Msty Studio 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 your agent picks the right machine before it burns an hour.
• File courier (Pro) for checkpoints and diffs up to 100 MiB.
• Outbound-only agent on each machine — no inbound ports, no exposed SSH, no VPN to set up.

Not a replacement — a multiplier

FAQ