Ship components from your terminal.
OonkooUI is a standard shadcn registry — free components install keyless with the CLI you already use. The oonkoo CLI does everything shadcn does, plus what it can't: sign-in, purchases, licenses, and verified downloads.
❯ npx oonkoo buy liquid-ether → Liquid Ether — $1 (one-time, lifetime updates) Checkout: https://checkout.stripe.com/c/pay_… ⠸ Waiting for payment… ✔ License granted — 'liquid-ether' is yours. ? Install 'liquid-ether' into this project now? › Yes → npx shadcn@latest add --yes @oonkoo/liquid-ether ✔ Created components/oonkoo/liquid-ether.tsx
Pick your CLI
Both work against the same registry — every component, same files. The oonkoo CLI wraps shadcn for installs, so choosing it costs you nothing.
oonkoo CLI
npx oonkoo …
- ✓ Full-screen terminal UI — run bare
npx oonkoo - ✓ Everything the shadcn CLI does (installs delegate to it)
- ✓ One-command sign-in — device flow or API key
- ✓
buypro components without leaving the shell - ✓ License library + sha256-verified codebase downloads
- ✓ Friendly errors: "unlock at …" instead of fetch failures
- ✓ Auto-wires components.json and .env.local
shadcn CLI
npx shadcn@latest …
- ✓ Already in your workflow — zero new tools
- ✓ Free components keyless
- ✓ Pro components with
OONKOO_API_KEYin the registry header - ✓ Search + MCP for AI agents
- ✗ No purchases, library, or zip downloads
- ✗ Raw errors when a pro item isn't unlocked
The terminal UI
Run bare npx oonkoo — the whole registry becomes a full-screen app.
╭─────────────────────────────────────────────────╮ │ ⏺ OONKOO UI v2.1.0 ● cool@swift.dev │ ╰─────────────────────────────────────────────────╯ ╭─ sections ──╮ ╭─ store ──────────────────────╮ │ 1 Free 11 │ │ ❯ liquid-ether pro $49 │ │ 2 Store 1 │ │ │ │ 3 Library │ │ WebGL fluid background. │ │ 4 Account │ │ enter buy · lifetime updates │ │ 5 Help │ ╰──────────────────────────────╯ ╰─────────────╯ ↑↓ move tab section enter action q quit
Browse free components and the store, install or buy with enter, download owned codebases from Library, and sign in or out from Account — all without leaving the keyboard. There may or may not be a hidden command that prints the logo.
Free components
No account, no key — one registry entry.
Register the @oonkoo registry
npx oonkoo init does this for you (and runs shadcn init first if needed) — or add it by hand:
{
"registries": {
"@oonkoo": "https://ui.oonkoo.com/r/{name}.json"
}
}Install anything free
# with the oonkoo CLI ❯ npx oonkoo add border-beam ✔ Created components/oonkoo/border-beam.tsx # or plain shadcn — same result ❯ npx shadcn@latest add @oonkoo/border-beam ✔ Created components/oonkoo/border-beam.tsx
Pro components
Buy once on the store or in the terminal — install forever.
Sign in
❯ npx oonkoo auth Your code: QZXF-TPLM Sign in at: https://auth.oonkoo.com/… ⠸ Waiting for browser sign-in… ✔ Logged in as you@company.com (device flow)
Headless or CI? Create a key at Settings → API Keys and set OONKOO_API_KEY — or run oonkoo auth --key.
Buy from the terminal
oonkoo buy opens Stripe Checkout, waits for your license, then offers to install — the loop from the demo above. Already bought on the web? Skip straight to oonkoo add.
Install what you own — and know what happens when you don't
❯ npx oonkoo add liquid-ether → npx shadcn@latest add @oonkoo/liquid-ether ✔ Created components/oonkoo/liquid-ether.tsx # without a key: ✖ liquid-ether: 'liquid-ether' is a paid component and requires an OonkoO API key. Create one at ui.oonkoo.com/settings/api-keys … # with a key, before purchasing: ✖ liquid-ether: 'liquid-ether' is a Pro component — unlock it at ui.oonkoo.com/components/oonkoo-store/components/liquid-ether Own it in one step: oonkoo buy liquid-ether
Delivered pro files carry a license header with your license key, and every registry response includes per-file sha256 checksums. Templates are the one exception — they ship as a full codebase via oonkoo download, not registry files.
Command reference
Twelve commands, zero config files — or just run npx oonkoo for the interactive UI. Hover to copy.
The full-screen terminal UI — browse, buy, and manage visually.
Wire AI agents (Claude Code, Cursor) to the registry.
Sign in — browser device flow, or --key for an API key.
Which account is signed in, and via what method.
Remove stored credentials from this machine.
Wire @oonkoo into components.json + scaffold .env.local.
The whole catalog, grouped, with tiers and prices.
Find components by name or description.
Install via shadcn, with commerce-aware errors.
Checkout → license → install, without leaving the shell.
Every license you hold, with keys and dates.
Owned codebase.zip, sha256-verified on arrival.
Every read command takes --json for scripting. Point at another environment with OONKOO_REGISTRY_URL.
Prefer plain shadcn? CI pipelines?
The companion CLI is optional. With the auth header on the registry entry and OONKOO_API_KEY in the environment, npx shadcn@latest add @oonkoo/<name> installs everything you own — locally and in CI.
{
"registries": {
"@oonkoo": {
"url": "https://ui.oonkoo.com/r/{name}.json",
"headers": {
"Authorization": "Bearer ${OONKOO_API_KEY}"
}
}
}
}Using an AI agent?
Claude Code and Cursor can search and install the whole catalog through the shadcn MCP server — same components.json, same key.
System
Node.js 18+ · npm, yarn, pnpm, or bun
Project
React 18+ · Tailwind 3+ · TypeScript recommended
Frameworks
Anything the shadcn CLI supports — Next.js, Vite, Remix, Astro…
Next: build with AI
Wire up your AI agent next — or jump straight into the library.