mcp

Overview ¶

osctrl-mcp serves osctrl's read-only surface over the Model Context Protocol, so an MCP client (Claude Code, Claude Desktop, or any other) can inspect a fleet through osctrl-api.

It speaks MCP over stdio and is meant to be launched by the client, not run as a daemon. It holds no state and opens no listening socket; every request becomes an authenticated call to osctrl-api, so the token's existing per-environment permissions are what bound the agent.

Give it a service user scoped to what the agent should read. It never issues a write, but a token that can write is still a token the process holds in memory.