Drive every command through typed MCP tools

Every devctl command that reaches the controller has a Control Room and operator MCP tool with the same name, schema, route and authorization. Agents call schedules, reviews, accounts, hosts, Projects and networks directly instead of composing raw API requests.

A typed tool keeps the authorization of its route and grants nothing its caller could not already do. Control Room cannot register MCP servers, credential profiles or bindings. How well Control Room Main uses the larger tool list in live work has not been proven yet.

How it works

  1. One registry for CLI and MCP

    A single operation registry derives the typed MCP tools and the CLI commands with the same route authorization. A parity test fails when a command or a tool lacks its counterpart.

  2. Check the inventory

    The published inventory lists 476 CLI commands and 439 MCP tools in 0.1.166. 451 commands have a tool; the 25 CLI-only commands stay that way by design, each with a written reason.

  3. Follow queued work

    Operations that return a command ID share get_command_result, so an agent can follow a queued Host command to its result.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.