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.

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: Msty Studio stays your model hub and chat — local or cloud models; AI Commander is the hands on the box — servers, GPU rigs, NAS, laptops — with no inbound ports and no exposed SSH.

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).
Msty Studio → Toolbox → Add New Tool → HTTP
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):

Msty Studio → Toolbox → Add New Tool → STDIO / JSON
{
  "command": "npx",
  "args": ["-y", "@aicommander/mcp"],
  "env": {
    "AICOMMANDER_TOKEN": "<your-api-key>"
  }
}

Get the details right

By default, API keys and OAuth connectors only act while the account owner has opened the AI Commander dashboard within its access window (72 hours by default; 24 h, 48 h or 7 days in the dashboard → Security tab; the gate can also be disabled) — 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

Not a replacement — a multiplier

You already useAI Commander adds
Msty StudioToolbox → Add New Tool → HTTP → https://aicommander.dev/mcp
Claude Codeclaude mcp add --transport http … → remote exec + jobs
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec

How Msty handles MCP servers

Checked against Msty docs: Toolbox tools in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits Msty

Msty is popular for running local models. Pairing it with AI Commander keeps the model on your desk and the commands on the machines that need them.

  1. Add aicommander to the Toolbox as a Streamable HTTP tool with your Authorization: Bearer API key header.
  2. Open the Tool Console and call list_machines once, to confirm the connection before any model is involved.
  3. Put AI Commander in a small "Ops" toolset, enable it in a chat with a tool-capable local model, and ask for routine checks such as service status or log tails through remote_exec.

Limits and gotchas in Msty

FAQ

Is AI Commander an alternative to Msty Studio?
No. AI Commander is NOT an alternative to Msty Studio. It is a remote-machine harness. You keep Msty Studio and your models (or Claude Code, Codex, ChatGPT, Cursor, and the other clients on /howto/) as your AI front end. AI Commander gives those tools secure remote shell, detached jobs, and file transfer on machines you own — over MCP or REST. It is also not an alternative to Claude Code, Codex, or ChatGPT; it works with them the same way.
How do I connect Msty Studio to AI Commander?
Open the Toolbox, click Add New Tool, choose HTTP and enter https://aicommander.dev/mcp, with an Authorization: Bearer API key header (or use https://aicommander.dev/mcp?anonymous=1 without a header for a code-only first hour). Then add the tool to a toolset and select that toolset in your chat. A local stdio bridge (npx -y @aicommander/mcp) works too through STDIO / JSON.
Does Msty Studio support remote MCP servers?
Yes. Msty Studio's Toolbox connects to remote MCP servers over Streamable HTTP and to local servers over STDIO / JSON. SSE is not supported, which does not matter here because AI Commander's endpoint is Streamable HTTP.
Why doesn't my model call AI Commander in Msty?
Check that the AI Commander tool is in a toolset and that the toolset is enabled in the current chat, with a tool-capable model. The Tool Console shows whether the tool itself responds.
Why does the npx-based AI Commander bridge fail to start in Msty?
Msty recommends managing Node with Volta rather than NVM, and Sidecar logs show the startup error. Or use the remote https://aicommander.dev/mcp endpoint with an API key header and skip Node entirely.

Next steps

Install the agent on a machine you control, add AI Commander to the Msty Toolbox as an HTTP tool (https://aicommander.dev/mcp), then ask your model for a real task on a remote box.