> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mzizi.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Browsing components

> How to list and inspect Mzizi registry components — on mzizi.dev, from the HTTP API, and from the MCP server.

[mzizi.dev/components](https://mzizi.dev/components) lists every registry component on one
page, grouped by the node of the helix it sits on, each with its install command. Each
component has its own page there, `mzizi.dev/components/<name>`. The API endpoints below cover
the same ground from a script.

## Install any component

```bash theme={null}
npx shadcn@latest add https://api.mzizi.dev/v1/ui/<component-name>
```

## List programmatically

```bash theme={null}
# Registry index — every item, metadata only
curl https://api.mzizi.dev/v1/ui

# A single component, with inline source
curl https://api.mzizi.dev/v1/ui/button

# The Rust (Dioxus) source, where one exists
curl https://api.mzizi.dev/v1/rs/button
```

`/v1/ui/{name}/docs` answers with the component's use cases, variants and accessibility notes.
`/v1/ui/{name}/versions` answers `503`, because version history is console data; see
[the API gateway](/platform/api-gateway#one-route-answers-503) for why.

The index response is a shadcn registry document: components sit under `items`, each with
`name`, `type` and `description`. The per-component response adds the full source in
`files[].content`.

<Note>
  The index is not an array. `GET /v1/ui` returns `{ "$schema": …, "name": "mzizi",
      "homepage": …, "items": [ … ] }`, and a client that decodes it as a bare list decodes it to
  nothing — which then renders as an empty gallery rather than an error. This has bitten a
  real consumer; decode the envelope.
</Note>

## Naming

Component naming is a deliberate mix. Framework-standard primitives keep their plain shadcn
names — `button`, `dialog`, `card` — while many brand composites carry the `mzizi-` prefix.
Components once named `nyuchi-*` were renamed `mzizi-*` on 27 September 2026, and the old
names answer `308` to the new ones.

## Over MCP

An agent can reach the same catalogue through the MCP server rather than the HTTP API. See
[the MCP server](/toolchain/mcp).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.