Capítulo 103 de 108
Registry-operator side of MCP support: the shadcn MCP server works with any shadcn-compatible registry automatically, as long as a valid registry.json (or registry) file exists at the registry root.
https://acme.com/r/[name].json, the MCP server expects https://acme.com/r/registry.json (or registry with no extension) — a valid JSON file conforming to the registry schema.components.json#registries and run shadcn mcp init --client <name>; the same schema and CLI mechanics as normal add/view/search apply.{
"registries": { "@acme": "https://acme.com/r/{name}.json" }
}
| Client | Setup |
|---|---|
| Claude Code | configure registries, run mcp init --client claude, restart, debug via /mcp |
| Cursor | configure registries, run mcp init --client cursor, enable in Settings |
| VS Code | configure registries, run mcp init --client vscode, click Start |
| Codex | configure registries, manually edit ~/.codex/config.toml |
| OpenCode | configure registries, run mcp init --client opencode, restart |
title/description help AI assistants pick the right item.dependencies: lets MCP auto-install npm packages correctly.registryDependencies: signals relationships between items so MCP composes correctly (e.g. building a landing page from hero + features + testimonials)./docs/registry/registry-json automatically works with MCP.registry.json/registry).title/description/dependencies/registryDependencies are filled in.