CLI Reference

Global flags

Most write-capable commands also accept --dry-run to preview the diff without touching disk.

create (default)

Scaffold a new project.

npx create-turbo-stack [project-name] [--preset <url>] [--yes] [--no-install] [--dry-run]

A preset's registryPackages are materialized via add after scaffolding.

npx create-turbo-stack my-app
npx create-turbo-stack my-app --preset https://create-turbo-stack.dev/s/saas-starter.json

init

Adopt an existing Turborepo by analyzing it and persisting .turbo-stack.json.

npx create-turbo-stack init [path] [--force]

After init, the rest of the toolchain (add, remove, switch, upgrade) becomes available.

add

Add an app, package, integration, npm dependency, or a registry package by name (shadcn-style — see Registry Packages).

npx create-turbo-stack add <type|name> [name] [--dry-run]

app / package / integration prompt when run bare; pass the name (and flags below) to run non-interactively (CI, agents):

npx create-turbo-stack add app admin --type nextjs --port 3001
npx create-turbo-stack add package billing --type utils --app web
npx create-turbo-stack add integration analytics --value posthog --app web
npx create-turbo-stack add security                 # registry package
npx create-turbo-stack add @acme/feature-flags -y   # private registry
npx create-turbo-stack add dependency lodash --to=apps/web

remove

Remove an app, package, or integration. Stale files are deleted, empty directories are pruned, .turbo-stack.json is rewritten.

npx create-turbo-stack remove <type> [name] [--dry-run]

switch

Atomic provider swap — old files deleted, new files written, in one transaction.

npx create-turbo-stack switch <category> [value] [--dry-run]

Categories: db | auth | api | analytics | errorTracking | email | rateLimit | ai.

npx create-turbo-stack switch db prisma          # was drizzle, becomes prisma
npx create-turbo-stack switch email nodemailer   # was resend, becomes nodemailer

upgrade

Migrate the project's preset to the current schema version. Walks the registered migration chain, validates the result, then re-applies the resolved file tree.

npx create-turbo-stack upgrade [--dry-run]

Idempotent. On a project already at the current version, it reports "nothing to do" and exits.

reconcile

Report how the project on disk diverges from .turbo-stack.json — packages/apps recorded in state but missing on disk, or on disk but untracked, plus expected files that are absent. Read-only (writes nothing); drift happens via manual edits, deletions, failed applies, or external tooling. Run it when add/remove/switch seem to produce wrong diffs.

npx create-turbo-stack reconcile [--json]

info

One-screen summary of the project's stack — schema version, basics, integrations, app/package counts. Read-only; safe in CI.

npx create-turbo-stack info [--json]

list

Every app type and integration provider currently registered (built-in plus plugins loaded from create-turbo-stack.json).

npx create-turbo-stack list [--json]

doctor

Environment + project sanity checks: Node version, package manager binaries, .turbo-stack.json validity, missing workspace directories, schema version drift. Exits non-zero on any fail-level finding — wire it into CI.

npx create-turbo-stack doctor [--json]

analyze

Reverse-engineer an existing Turborepo into a preset JSON without persisting state. Use init if you want to write .turbo-stack.json instead.

npx create-turbo-stack analyze [path] [--json] [--open-builder] [--diff <file>]

preset

Save or validate a preset JSON.

npx create-turbo-stack preset save [file]
npx create-turbo-stack preset validate <file>

mcp

Start the Model Context Protocol server over stdio. Pin the project root with TURBO_STACK_ROOT=/path/to/project when launching from a client (Claude Desktop, Cursor) — otherwise the server uses the client's cwd, which is rarely your project.

TURBO_STACK_ROOT=/path/to/project npx create-turbo-stack mcp

Tools are prefixed with turbostack_ to avoid global namespace collisions on the client side.

Generated files at a glance