Other MCP clients

Any MCP-capable client that can spawn a stdio server can use Cmdop’s fleet integration. Configure the client to start:

cmdop mcp stdio

The client must be able to find the cmdop executable and the machine must already have joined a relay. Cmdop does not publish a local HTTP MCP endpoint for this integration.

The server offers fleet operations—not a local editor or terminal tool catalogue. Verify the exact operations for the installed version with:

cmdop mcp tools

For assistants with built-in registration support, prefer cmdop mcp install. If a client-specific configuration format changes, use that client’s current documentation for the config file and keep its entry limited to the stdio command above.

Cmdop registers itself automatically only in Claude Code and Codex. For every other client — Cursor, VS Code, Windsurf, Zed, the Cline family, Gemini CLI, Claude Desktop — add the stdio entry yourself using that client’s own configuration format.

Those same clients are the ones cmdop mcp discover can read when you want to go the other way and reuse an MCP server they already have. See External MCP tools.

Common questions

How do I connect another MCP client to Cmdop?

Configure the client to spawn cmdop mcp stdio. The client must be able to find the cmdop executable, and the machine running it must already have joined a relay.

Does Cmdop expose a local HTTP MCP endpoint?

No. This fleet integration is stdio. Cmdop does not publish a local HTTP MCP endpoint for other clients to call.

Are other MCP clients given local shell access?

No. Cmdop’s MCP server exposes fleet operations, not a local editor, terminal, or filesystem tool catalogue. Check the installed tool list with cmdop mcp tools.