Consuming the registry
Install components into your app with the shadcn CLI.
The Mzizi portal is a shadcn-compatible component registry that serves the full set of stable registry items across 10 architecture layers. The live count is published at GET /api/v1/stats. It allows any app in the bundu ecosystem to install production-ready components with a single CLI command — consumed by mukoko’s 17 mini-apps, nyuchi’s 7 enterprise products, and other ecosystem brands. It ships the Bundu floor 1.1.0 values in registry 4.45.0.
The registry serves components in two ways:
GET /api/v1/ui/{name} reads registry.json at runtime, inlines component source code, and serves it with CORS headerspnpm registry:build pre-generates JSON files into public/r/ for CDN servingBoth formats are compatible with the shadcn CLI.
registry.json (manifest — source of truth) │ ├── Dynamic API (app/api/v1/ui/) │ ├── GET /api/v1/ui → registry index │ └── GET /api/v1/ui/{name} → component JSON with source │ └── Static build (scripts/build-registry.js) └── public/r/{name}.json → pre-built component JSONConsuming the registry
Install components into your app with the shadcn CLI.
Contributing components
Author and publish new registry components.
Registry schema
The shadcn-compatible JSON schema the registry follows.
MCP server
Expose the registry to AI assistants over the Model Context Protocol.
npx shadcn@latest add https://mzizi.dev/api/v1/ui/buttonThis fetches the button component JSON, resolves its dependencies (radix-ui, class-variance-authority), and writes components/ui/button.tsx to your project.