Connect Cmdop through MCP
On a machine that has joined the fleet, register Cmdop with a supported local assistant:
cmdop mcp install --agent codex
cmdop mcp status
cmdop mcp toolsUse --agent claude for Claude Code, or omit --agent to target detected
supported assistants. Start a new assistant session after registration.
cmdop mcp tools prints the fleet operations exposed by the installed Cmdop
version. The registration launches cmdop mcp stdio as a subprocess; you do
not need to run that command separately or open a network port.
To see what MCP configuration your installed assistants already have, without starting any of them:
cmdop mcp discoverRemove a registration with:
cmdop mcp uninstall --agent codex
cmdop mcp statusThe separate cmdop mcp servers tree manages external MCP servers that Cmdop
agents may use. See External MCP tools before
adding or approving one.
What gets registered
The registration points your assistant at the installed cmdop binary. That
means the assistant sees the machine and relay context this CLI is configured
to use; it does not create a new cloud account, expose a local port, or copy
credentials into the assistant’s prompt.
Re-run cmdop mcp status after upgrading either Cmdop or the assistant. If the
assistant cannot see the tools, restart its session first, then inspect the
generated MCP configuration.
Cmdop