# Introduction

> The jurniti developer CLI — one binary that drives provisioning, billing, VMs, and templates, and doubles as an MCP server for your own agent.

Part of the jurniti developer docs — canonical page: https://www.jurniti.com/docs · full docs index: https://www.jurniti.com/docs/llms.txt

## One CLI. Every operation. The same verbs for your agent.

**jurniti** is the secure managed agent platform: your agent runs in a real
Firecracker microVM with your own model keys. The `jurniti` CLI is how you drive
it from a terminal, a CI job, or your own agent — no dashboard round-trip
required.

### One vocabulary

Every operation exists in exactly one shape, spelled the same everywhere:

- A **CLI verb** — `jurniti up`, `jurniti vms ls`, `jurniti fork`.
- The **same verb as an MCP tool** — mount the binary once (`claude mcp add
  jurniti -- jurniti mcp`) and your agent gets the identical command set.
- A **REST noun** underneath — the CLI and MCP server are thin clients over the
  same tenant API.

Learn one and you know all three. There is no separate "API concept" to relearn
when you move from the terminal to your agent.

### Where to start

  - [Installation](/docs/installation): One line to install the CLI on macOS or Linux.
  - [Quickstart](/docs/quickstart): Log in, add a card, and bring your first agent VM up.
  - [CLI reference](/docs/cli-reference): Every verb the binary ships, sourced from the CLI itself.
  - [MCP](/docs/mcp): Give your own agent the exact same commands as tools.

> **No free tier — a guarantee instead:** Bringing a VM up needs a card on file. There is no free trial and no free tier; every plan ships a **30-day money-back guarantee** on your first subscription instead. See [Quickstart](/docs/quickstart) for the exact gate.