Ondo UI is an open-source design system with a warm, trustworthy mood. It's built so everyone — from the youngest users to the oldest — can reach for it comfortably and with confidence, never finding it unfamiliar or heavy. Designed for both desktop and mobile, it ships components, tokens, and themes as a shadcn registry, so design and code always share one source.
Designers build screens on top of Ondo UI's components and tokens; developers install those same registry components through the shadcn MCP and implement the design as-is. The two don't build separate things — they stay aligned on a single source.
Ondo UI isn't tied to any one domain. It suits any product used across a wide range of ages, or wherever comfort and trust matter most. Where clarity beats flash and ease beats complexity — on web or app alike — it carries one consistent mood.
"Ondo" means temperature — the work of keeping every product's mood at one steady warmth. Tokens as °C, light and dark as Warm and Cool: one brand, felt as a single temperature.
Ondo UI sits at the center of a design–development loop. Both the design team and the dev team access the same registry through the shadcn MCP: the design team designs product screens on top of Ondo UI's components and tokens, and the dev team implements those designs with the exact same registry components — so design and code always share a single source of truth.
flowchart TD
classDef default fill:#4a90d9,stroke:#6ab0ff,color:#fff
subgraph ondo["🌡️ Ondo UI"]
registry["Component & Theme Registry<br/>registry.json"]
end
mcp["🔌 shadcn MCP"]
subgraph design["🎨 Design Team"]
mockup["Product Screen Design"]
end
subgraph dev["🛠️ Dev Team"]
add["Browse & install components<br/>(npx shadcn@latest add)"] --> product["Product Implementation"]
end
registry -->|"components & tokens"| mcp
mcp --> mockup
mcp --> add
mockup -->|"design handoff"| add
design -.->|"new components & improvement proposals"| ondo
- Ondo UI publishes components, themes, and tokens as a shadcn registry.
- Both the design team and the dev team access the same registry through the shadcn MCP.
- The design team designs product screens on top of Ondo UI components and hands them off to the dev team.
- The dev team browses components via the MCP and installs them with
npx shadcn@latest addto implement the designs. - New components and improvements proposed during design flow back into Ondo UI, and the loop repeats.
Two steps make the Ondo UI registry available to AI tools (Claude Code, Cursor, etc.).
1. Register the registry — add the @ondo-ui namespace to your project's components.json:
{
"registries": {
"@ondo-ui": "https://ui.ondo.dou.so/r/{name}.json"
}
}2. Register the MCP server — run the command for your client:
npx shadcn@latest mcp init --client claude # Claude Code
npx shadcn@latest mcp init --client cursor # Cursor
npx shadcn@latest mcp init --client vscode # VS CodeOnce configured, just ask your AI in natural language:
- "Show me the components in the @ondo-ui registry"
- "Add @ondo-ui button and card to this page"
See the installation docs for details.
To add components to your app, run the following command:
npx shadcn@latest add buttonThis will place the ui components in the components directory.
To use the components in your app, import them as follows:
import { Button } from "@/components/ui/button";