SlopBurn CLI

slopburn is a first-class CLI for SlopBurn with dedicated onboarding and MCP config, while reusing Cutline's auth/runtime components under the hood.

Install

npm i -g @vibekiln/slopburn-cli

For staging:

npm i -g @kylewadegrove/slopburn-cli-staging

Commands

• slopburn setup [--staging] [--serve-now]
  Writes MCP config entries for only the slopburn server, saves channel preference in ~/.slopburn/config.json, writes project-local game defaults to .cutline/slopburn.json, and installs .cursor/rules/slopburn-intents.mdc so natural-language prompts route to SlopBurn MCP tools.
  • --serve-now launches the MCP server immediately after setup to reduce handoff friction.
  • --verbose prints the longer setup summary.
• slopburn login [--staging]
• slopburn status [--staging]
• slopburn logout [--staging]
• slopburn serve [--staging] [--project-root <path>] [--http --host --port --path] [--verbose]
• slopburn bootstrap [--project-root <path>] [--full]
• slopburn event <title|level-up|game-over|encounter|victory> (renders local terminal banners/audio cues)

How it works

• setup writes slopburn MCP entries separately from cutline-* entries.
• Generated MCP config calls slopburn serve directly instead of wrapping startup in npx.
• serve delegates to Cutline MCP components via:
  • production: @vibekiln/cutline-mcp-cli
  • staging: @kylewadegrove/cutline-mcp-cli-staging
• slopburn now bundles both Cutline CLI packages as dependencies, so one global install is enough.
• Runtime prefers the bundled local dependency and only falls back to npx resolution if needed.

This keeps SlopBurn onboarding/config independent while still leveraging shared Cutline internals.

Startup Model

• ~/.slopburn/config.json stores machine-local CLI state like the preferred channel.
• .cutline/slopburn.json stores project-local game defaults such as:
  • onboarding mode
  • default character name/class
  • optional project/product linkage
  • quiet/auto-resume startup preferences
• MCP startup reads the project-local config, so the same defaults work whether SlopBurn is launched from slopburn serve or from your IDE MCP config.

First-Time Setup

slopburn setup --serve-now

Then refresh your MCP/chat session and say:

start slopburn

If you want the longer reference output, run:

slopburn bootstrap --full

Returning User

If .cutline/slopburn.json already exists, setup reuses it and avoids repeating character questions:

slopburn setup --serve-now

Then refresh your MCP/chat session and say:

start slopburn

Natural-language start prompts

After slopburn setup, you can say these directly in your AI chat:

• start slopburn
• take a turn in slopburn for this feature idea
• roll tests as the dungeon check for my run
• show my spellbook and equip the best offered spell