Keep TypingMind.
Give your agents your machines.

AI Commander is not an alternative to TypingMind, 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, JetBrains Junie, Kiro, Warp, Factory, Crush, LM Studio, Trae, Claude Desktop, n8n, OpenAI Agents SDK, Visual Studio, JetBrains AI Assistant, Open WebUI, LibreChat, or AnythingLLM. 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: TypingMind stays your chat front end, your models and your agents; AI Commander is the hands on the box — servers, GPU rigs, NAS, laptops — with no inbound ports and no exposed SSH.

Sibling harness pages: AnythingLLM · LibreChat · Open WebUI · LM Studio · Claude Code · Codex · ChatGPT · Claude Desktop — and the rest on Connect your AI client.

Connect TypingMind (remote MCP, custom connector)

TypingMind connects to remote MCP servers over streamable HTTP and shows each connection as a plugin you can use in any chat (TypingMind docs: MCP in TypingMind). If AI Commander isn’t listed in the MCP Store, add it by hand:

Open Plugins → MCP Store and click Add custom connector.
Enter the server URL https://aicommander.dev/mcp.
Personal version only: if TypingMind asks you to pick an MCP connector, choose TypingMind Cloud (free account sign-up) or your own Private MCP Connector.
Sign in when TypingMind opens the AI Commander login. TypingMind registers itself through OAuth Dynamic Client Registration, which AI Commander supports, and refreshes the token for you.

TypingMind → Plugins → MCP Store → Add custom connector

URL:   https://aicommander.dev/mcp
Auth:  OAuth (sign in to AI Commander)
   or  header  Authorization: Bearer <your-api-key>

Prefer an API key over OAuth? Create one in the AI Commander dashboard (see Accounts & API keys) and send it as an Authorization: Bearer header. With either, the agent can list your machines and reach them by alias. No account yet? Use https://aicommander.dev/mcp?anonymous=1 for a code-only first hour.

Why TypingMind asks for a connector

TypingMind runs in your browser, and most MCP servers — AI Commander’s endpoint included — do not accept direct cross-origin calls from a web page. In the Personal version TypingMind therefore sends MCP traffic through a connector: TypingMind Cloud, or the self-hosted Private MCP Connector that you run yourself with npx @typingmind/mcp <auth-token> on the same device or on a private server (TypingMind docs: Private MCP Connector).

Get the details right

Pick your tools: TypingMind lets you switch individual MCP tools on or off in the connection’s tool list.
Long work: TypingMind ends idle MCP sessions after 5 minutes, so start detached jobs (remote_job_start, then remote_job_status / remote_job_logs) instead of one long tool call.
Team version: MCP servers are admin-managed plugins in TypingMind for Teams; one API key is one AI Commander account, so everyone who gets that plugin acts as that account. Where your setup lets each user sign in with OAuth, prefer that so everyone acts as their own account.
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 TypingMind versions — check the linked TypingMind 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 TypingMind 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

You already use	AI Commander adds
TypingMind	Plugins → MCP Store → Add custom connector → `https://aicommander.dev/mcp` + OAuth
AnythingLLM	`mcpServers.aicommander` → `"type": "streamable"`, `"url": "https://aicommander.dev/mcp"` in `anythingllm_mcp_servers.json`
LibreChat	`mcpServers.aicommander` → `type: streamable-http`, `url: https://aicommander.dev/mcp`, OAuth
Claude Code	`claude mcp add --transport http …` → remote exec + jobs
Codex / ChatGPT	Same MCP endpoint or REST `/api/v1/exec`

FAQ

Is AI Commander an alternative to TypingMind?

No. AI Commander is NOT an alternative to TypingMind. It is a remote-machine harness. You keep TypingMind, your chats, agents and models (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, JetBrains Junie, Kiro, Warp, Factory, Crush, LM Studio, Trae, Claude Desktop, n8n, OpenAI Agents SDK, Visual Studio, JetBrains AI Assistant, Open WebUI, LibreChat, or AnythingLLM) 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 TypingMind to AI Commander?

Open Plugins → MCP Store → Add custom connector and enter https://aicommander.dev/mcp. TypingMind registers itself through OAuth Dynamic Client Registration, which AI Commander supports, so you sign in to your AI Commander account in the pop-up; an API key in an Authorization: Bearer header also works. In the Personal version TypingMind may ask you to pick an MCP connector the first time (TypingMind Cloud or your own Private MCP Connector). See /howto/ for the full matrix.

Why does TypingMind ask me for an MCP connector?

TypingMind runs in the browser, and most MCP servers — AI Commander's endpoint included — do not accept direct cross-origin calls from a web page. TypingMind's docs therefore route Personal-version MCP traffic through a connector: TypingMind Cloud (free account sign-up) or the self-hosted Private MCP Connector (npx @typingmind/mcp <auth-token>) on your own device or server.

Can I limit which AI Commander tools TypingMind uses?

Yes. TypingMind lets you enable or disable individual tools of an MCP server in its tool list. Long work should go through detached jobs (remote_job_start, then remote_job_status or remote_job_logs), because TypingMind ends idle MCP sessions after 5 minutes.

Next steps

Install the agent on a machine you control, add AI Commander in TypingMind’s MCP Store as a custom connector (https://aicommander.dev/mcp), then ask your agent for a real task on a remote box.

Install the agent Setup guides Remote coding agents

Keep TypingMind.Give your agents your machines.