oz0 mcp
For: Operators and developers looking up a command.
Serve the operators' MCP server on stdin and stdout, as an MCP client starts a local server: claude mcp add orchestrator-zero -- oz0 mcp.
Each request goes to the management port's MCP endpoint (https://<management>/admin/mcp) with the CLI context's operator certificate, so the tools act as that operator, with the same rights as the CLI: read nodes, jobs and why they wait, plugins, rollouts, costs, quotas, the audit log and findings; block and unblock nodes, cancel and retry jobs, start and roll back rollouts, decide approvals and set kill switches.
Destructive tools ask the person to confirm when the client can (elicitation), and need "confirm": true otherwise. Every call is in the audit log with via: mcp. Logs go to stderr.
Usage
oz0 mcp [flags]
oz0 mcp [command]
Subcommands
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--url | string | the context's management address and /admin/mcp | the MCP endpoint |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.