rune new.
One command, one server.
rune new is the entire CLI. Pick a preset,
answer the prompts or skip them with --yes,
and walk away with a project that boots on the first try.
› rune new my-server --preset simple --yes Scaffolding my-server (simple)… ✓ wrote files to /Users/dsaenz/Code/my-server ✓ initialized git repo running npm install… ✓ installed dependencies Next steps: cd my-server npm run start:local
rune new. There is no second command to learn — and no plan to add one.simple for the fastest boot the framework allows. advanced for the full kit. You pick one and move on.npm run start:local works. No "next, you'll need to…" step after the scaffold.--mcp-rune-local at a clone of mcp-rune and your scaffold reads from disk. Built for the pre‑1.0 contributor workflow.Simple or advanced.
The only decision the scaffolder asks you to make. Everything else is a prompt you can skip.
For trying the framework right now. The smallest thing mcp‑rune can boot — a single transport, one example model, zero prompts asked. Start here when you want to see it work before committing to anything.
› rune new my-server --preset simple --yes Scaffolding my-server (simple)… ✓ wrote files ✓ initialized git repo ✓ installed dependencies Next steps: cd my-server npm run start:local
For a server you intend to keep. HTTP transport with OAuth, your own named models, optional analysis and domain modules. Start here when you know what you're building and want the infrastructure from day one.
› rune new my-server --preset advanced ✓ Models to scaffold (comma-separated) book,shelf,home ✓ Transport? both (recommended) ✓ Enable analysis? Yes ✓ Enable domain? Yes Scaffolding my-server (advanced)… ✓ wrote files ✓ initialized git repo ✓ installed dependencies
--yes skips them all
and takes the defaults.
That's the whole CLI.
The full reference — every flag, every prompt default, every generated file — lives in the docs.