sora-cli is a standalone CLI for installing components from any shadcn-compatible registry into your project. It defaults to the Sora UI registry, so it skips the extra step of registering the @soralabs scope that the shadcn CLI needs — but it also works against any other registry via --registry <url>.

Commands

# multiple components in one call
npx @soralabsoss/sora-cli add text-effect draw-underline-link

# interactive picker — no component names, browse and multi-select
npx @soralabsoss/sora-cli add

# list every component available in the registry
npx @soralabsoss/sora-cli list

# compare installed files against the current registry version
npx @soralabsoss/sora-cli diff text-effect

# diagnose common project setup issues
npx @soralabsoss/sora-cli doctor

add

Resolves the dependency tree for the requested component(s), writes files into your project, and installs npm dependencies with your detected package manager (bun/pnpm/yarn/npm).

npx @soralabsoss/sora-cli add text-effect --path src/components/ui
npx @soralabsoss/sora-cli add card --cwd packages/ui       # run as if started in packages/ui (monorepos)
npx @soralabsoss/sora-cli add text-effect --force           # overwrite existing files without asking
npx @soralabsoss/sora-cli add text-effect --yes              # skip the install confirmation, for scripts/CI
npx @soralabsoss/sora-cli add text-effect --dry-run          # preview what would change, write nothing
npx @soralabsoss/sora-cli add text-effect --silent            # only print summary lines, not per-file output
npx @soralabsoss/sora-cli add text-effect --view              # print file contents instead of writing them

list

Lists every component the target registry exposes. Add --json for machine-readable output (safe to pipe — errors and status messages go to stderr, never mixed into the JSON on stdout).

npx @soralabsoss/sora-cli list
npx @soralabsoss/sora-cli list --json

diff

Read-only comparison of installed component files against the current registry content — reports drift without writing anything.

npx @soralabsoss/sora-cli diff text-effect

If files differ, re-run add <component> --force --yes to apply the update.

doctor

Diagnoses common project setup issues before you install anything: Node version, package manager/lockfile conflicts, components.json validity, path alias configuration, Tailwind/React versions, cn() util dependencies, registry reachability, and whether a newer sora-cli version is available.

npx @soralabsoss/sora-cli doctor
npx @soralabsoss/sora-cli doctor --json

Options reference

Environment

SORA_NO_UPDATE_CHECK — set to disable the npm update check that runs on every invocation (printed to stderr, never mixed into --json output). Useful in CI.

How it works

The CLI fetches a shadcn-compatible registry (<product-url>/r/registry.json, <product-url>/r/<name>.json), resolves the dependency tree, writes files into your project, and installs npm dependencies with your detected package manager.

Since components are copied into your project rather than installed as a package, diff is the way to check whether the registry has changed a component since you installed it, and add <component> --force --yes is how you apply that update.

Registry content isn't cryptographically signed, so only point --registry at a source you trust — it's written into your project and its dependency list is fed straight into your package manager.

Monorepos

npx @soralabsoss/sora-cli add card --cwd packages/ui

See also

• Installation — initial project setup with shadcn/ui
• MCP — the get_component_info MCP tool returns the exact sora-cli command to run for a given component
• Troubleshooting — common registry/CLI issues
• GitHub repository