MCP
Mount the jurniti CLI as an MCP server so your own agent drives your fleet with the exact same verbs you use in the terminal.
Give your agent the same commands
The jurniti binary is also an MCP stdio
server. Mount it once and your own agent — Claude Code, or anything that speaks
MCP — gets the exact same verbs as tools. No second API to learn, no
separate SDK: the CLI verb, the MCP tool, and the REST noun are one vocabulary.
Mount it
claude mcp add jurniti -- jurniti mcpThat registers the CLI's built-in server (jurniti mcp) with your agent. From
then on your agent can provision, list, inspect, stop, capture, and fork VMs by
calling the same commands you would type.
Same verbs, now as tools
Every verb in the CLI reference is exposed as an MCP tool
with the same name and arguments. jurniti up becomes an up tool; jurniti vms ls becomes a vms ls tool; and so on. Your agent authenticates as you
(the API key on the machine), so it operates strictly within your tenant.
Your agent inherits your gate
The MCP server runs under your identity and your card. Provisioning tools
(up, fork) still start real, billed VMs — the same no-free-tier gate
applies whether a human or your agent invokes them.
Scope it with API keys
Mint a read-only key (jurniti keys issue) for an agent that should only
observe, or a read-write key for one that provisions. Rotate or revoke any key
with jurniti keys rotate / jurniti keys revoke.