Pick your on-ramp
Jetty is one API with several front doors. Everything below talks to the same backend ( https://flows-api.jetty.io ) and authenticates with the same token, so you can start with the plugin today and drop down to the SDK or REST API later without changing anything on the server side.
There are five ways in. Most builders start with the first one.
| On-ramp | Best for | You get |
|---|---|---|
| Claude Code plugin & skills | Claude Code users | /jetty commands, a guided /jetty-setup wizard, and the create-runbook / optimize-runbook skills. |
| MCP server | Cursor, VS Code, Windsurf, Zed, Codex, Gemini CLI | 16+ Jetty tools in any MCP-compatible agent, via npx -y jetty-mcp-server. |
| Client SDK | TypeScript / Node apps & CI | @jetty/sdk — a typed JettyClient with runAndWait() and the full run / trajectory / label surface. |
| REST API | Any language, any runtime | An OpenAI-compatible /v1/chat/completions endpoint with two modes. |
| Standalone CLI | Shell scripts & quick checks | source jetty-cli.sh for jetty_collections, jetty_run_sync, and friends — no install. |
One token, everywhere
Every on-ramp resolves your Jetty API token the same way, in this order:
- An explicit value you pass in code (SDK) or set inline (CLI).
- The
JETTY_API_TOKENenvironment variable. - The file at
~/.config/jetty/token, written by/jetty-setup.
Run /jetty-setup once (or grab a token from Settings → API keys) and every tool below just works. Point at a different backend with JETTY_API_URL if you need to.
How to choose
- In Claude Code? Install the plugin. It bundles the skills and the MCP server together and is the shortest path to a running runbook.
- In another editor or agent? Add the MCP server. Same tools, one line of config.
- Building an app, a CI check, or an eval harness? Use the SDK, or, if you're not on TypeScript, the REST API directly.
- Wiring an agent from another framework? See agent integrations, where the SDK is how you grade and store its output on Jetty.
All three of the plugin, the MCP server, and the standalone CLI live in one open-source repo: jettyio/jettyio-skills. The SDK lives in jettyio/jetty-sdk.