Bring Your Agent

> Guide me through installing https://www.jetty.io/agent-instructions.md and setting up my first runbook.

Machine Instructions

Get a token

Sign up at jetty.io, create a key under Settings → API keys (it looks like mlc_…), and export it so the CLI and SDK can find it:

export JETTY_API_TOKEN="mlc_…"

If your agent has the plugin installed, skip the dashboard: the jetty-setup skill below writes the token to ~/.config/jetty/token for you.

Install the plugin

The plugin is the fastest way to use Jetty from an agent. It bundles four skills and the MCP server together, so a single install gives you natural-language commands, a guided setup wizard, and the runbook-authoring loop without leaving your editor. The skills are plain markdown, so any agent that supports skills can load them: the repo carries plugin manifests for Claude Code, Codex, and OpenCode, and Antigravity loads them once they are copied into its skills directory.

In Claude Code, two commands add the marketplace and install the plugin:

claude plugin marketplace add jettyio/jettyio-skills
claude plugin install jetty@jetty

Then run the setup wizard once. It creates or links your account, writes your token to ~/.config/jetty/token, and checks that your model provider keys are in place. In Claude Code that is a slash command; in other agents, ask to “set up Jetty” and the agent picks the skill from its description:

/jetty-setup

That's it. The token it writes is the same one every other on-ramp reads, so the MCP server, the SDK, and the CLI are all configured at the same time.

Using an editor that speaks MCP but not skills, such as Cursor, VS Code, Windsurf, or Zed? Add the MCP server on its own and point the agent at agent-instructions.md for onboarding. The tools are identical; you drive the create and optimize loops in plain English instead of through a skill.

Jetty Skills

Each skill is a markdown file the agent reads on demand. In Claude Code they are slash commands; elsewhere, describe what you want and the agent matches the skill by its description.

jetty: natural-language workflow control

Talk to Jetty in plain English. The skill maps your request onto the underlying API, so you don't have to remember endpoints or JSON shapes.

/jetty list collections
/jetty list tasks in acme
/jetty run triage in acme with ticket="customer can't log in"
/jetty show the last run for triage

jetty-setup: first-run onboarding

The wizard you run once. Handles account creation, token storage, and a provider-key pre-flight so your first runbook doesn't fail on a missing key.

create-runbook: author a new runbook

Guided authoring for a brand-new runbook: it asks what you want done, what “done” looks like, and what to check, then writes a structured RUNBOOK.md with frontmatter and evals. See Runbooks for the anatomy.

optimize-runbook : Improving an existing runbook

It reads your prior runs, finds where they fall short of the runbook's evals, proposes targeted edits, and re-runs to confirm the score moved.

The plugin ships the same MCP server the rest of the editors use, so when you ask for a run through the jetty skill, your agent is calling the run-workflow MCP tool against flows-api.jetty.io. The skills are the guided layer on top; the MCP tools work in every editor.