AIOC exposes its entire monitoring surface as Model Context Protocol servers. Point any MCP-capable host at the command center and it can see the fleet, query the audit log, and act on escalations — oversight as tools, not dashboards.
Live fleet status, the agent registry, and quarantine controls.
Stream and query the event log — and push external events into the pipeline.
Work the exception queue from any MCP host.
Read and update governance policy and intervention flags.
Every human action and system decision, queryable.
Any MCP client — Claude Code, Claude Desktop, or your own agent — connects with a standard server entry. One API key, five servers.
The MCP surface is being built alongside the v1 console. Server names and tool signatures above are the draft contract and subject to change — pin your integration to the docs version, not this page.
See the command center running a live simulated fleet — or join the waitlist for early access.