shadcn Registry Directory
277 community shadcn registries, machine-readable at /r/registries.json
The official index of third-party shadcn registries. Every listed registry is built into the CLI with no configuration, so `npx shadcn add @<registry>/<component>` resolves straight away — @aceternity, @magicui, @cult-ui, @kokonutui, @neobrutalism, @kibo-ui, @shadcnblocks, @ai-elements, @spell, @8bitcn and 267 more. The rendered page is a client-side grid, but the same data is served as a flat JSON array at https://ui.shadcn.com/r/registries.json with name, homepage, URL template, and description per entry. The page also links the docs for running your own registry, namespaces, authentication, and the shadcn MCP server.
npx shadcn add @<registry>/<component>This is the first place to look before you hand-roll a component or pick a library from memory — fetch https://ui.shadcn.com/r/registries.json, not the HTML page, because the visible grid is rendered client-side and a plain fetch of /docs/directory returns prose with zero listings. Each record gives you a namespace, a homepage, and a URL template like https://shadcnblocks.com/r/{name}.json, so you can resolve any component to a real JSON payload before installing. Two cautions: inclusion is self-submitted and unvetted, so read the code the CLI writes; and a namespace being absent here (Origin UI, tweakcn, Watermelon UI) does not mean the registry is bad, only that it needs an explicit URL install.
Why it is here. It is the canonical machine-readable map of the shadcn ecosystem — 277 registries an agent can enumerate, filter, and install from without a single web search.
- 277 registries in one JSON array
- namespaces built into the CLI with zero config
- URL templates resolve any component to JSON
- self-submitted and explicitly unvetted
Verified 2026-08-15. HTTP 200. https://ui.shadcn.com/docs/directory (HTML, stripped of tags), https://ui.shadcn.com/r/registries.json (277 entries parsed)
