0

MCP Server

Use the @ondo-ui registry from AI assistants via the shadcn MCP server.

The shadcn MCP server works out of the box with the @ondo-ui registry. Once configured, AI assistants such as Claude Code, Cursor, and GitHub Copilot can browse the registry, look up component details, and install them into your project from natural-language prompts.

The MCP server discovers items through the registry index served at https://ui.ondo.dou.so/r/registry.json — nothing extra needs to be enabled on the registry side.

Register the registry

Add the @ondo-ui namespace to the registries field of your components.json. The MCP server reads this mapping to resolve the registry. If you already did this during installation, skip this step:

components.json
{
  "registries": {
    "@ondo-ui": "https://ui.ondo.dou.so/r/{name}.json"
  }
}

Set up your client

Run the following command in your project:

bunx --bun shadcn@latest mcp init --client claude

This creates a .mcp.json file with the shadcn MCP server configured.

Restart Claude Code and try the following prompts:

  • Show me the components in the ondo-ui registry
  • Build a login form using components from the ondo-ui registry

Note: You can use the /mcp command in Claude Code to debug the MCP server.

How it works

Every registry item ships with a description, its npm dependencies, and its registryDependencies, so the MCP server can explain what an item is for and install everything it needs in one step. For example, asking for @ondo-ui/alert-dialog also pulls in button and utils automatically.

You can read more about the MCP server in the shadcn MCP documentation.