Use with AI assistants
Let Claude Code, Cursor, VS Code, Codex or OpenCode search and install VenusUI components through the shadcn MCP server.
How it works
The shadcn CLI includes an MCP server. Your assistant uses it to list, search and read items from every registry in your components.json, and to get the command that installs them. Add @venusui to that file and VenusUI shows up next to the official shadcn components.
Run both steps inside a project that’s already set up with shadcn (it needs components.json and tsconfig.json). New project? Start with the Installation guide.
1. Add the @venusui registry
Once per project. It adds VenusUI to the registries in your components.json, so your assistant knows to look there. No address needed: the shadcn registry index supplies it.
npx shadcn@latest registry add @venusui2. Connect your assistant
npx shadcn@latest mcp init --client claudeSwap claude for your assistant. Each one stores the setup in a different place:
| Assistant | --client | Result |
|---|---|---|
| Claude Code | claude | Writes .mcp.json. |
| Cursor | cursor | Writes .cursor/mcp.json. |
| VS Code | vscode | Writes .vscode/mcp.json. |
| OpenCode | opencode | Writes opencode.json. |
| Codex | codex | Writes nothing. Prints a snippet to add to ~/.codex/config.toml yourself. |
For Claude Code the file looks like this. Restart your assistant afterwards so it picks the server up.
.mcp.json
{
"mcpServers": {
"shadcn": {
"command": "npx",
"args": [
"shadcn@latest",
"mcp"
]
}
}
}
3. Ask for components
Mention the registry by name so the assistant searches it. For example:
- “Find a pricing block in the @venusui registry.”
- “Show me what
@venusui/shimmer-buttoninstalls.” - “Add
@venusui/hero-10and use it on the home page.”
Behind the scenes it calls tools such as search_items_in_registries, view_items_in_registries and get_add_command_for_items, then runs the same npx shadcn@latest add command you would.
llms.txt
Assistants without MCP can read /llms.txt instead: a plain-text list of every guide, component, block and template with its description and install command.
Troubleshooting
- The assistant can’t find
@venusui - The registry is added per project. Run step 1 in the project the assistant has open, and check that
components.jsonlists@venusui. Failed to load tsconfig.jsonwhen runningmcp init- Run it from your project’s root, next to
components.jsonandtsconfig.json. - No shadcn tools show up
- Restart the assistant (or reload its MCP servers) after
mcp init.