AI Commander MCP server

Which servers in the official MCP registry are AI Commander's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to AI Commander

Whose server it is

Registry namedev.aicommander/mcpverified in the MCP registry

The registry name sits under aicommander.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Staterequires sign-inchecked 2026-10-13

On 2026-10-13 the server answered and asked for a sign-in with a AI Commander account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "aicommander": {
      "type": "http",
      "url": "https://aicommander.dev/mcp"
    }
  }
}

The first time it connects, the client opens a AI Commander sign-in.

Also shipped through: npm

OpenAPI spec

15 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.