Getting Started
MCP Server
Connect the shadcn MCP server to Cursor, Claude Code, or VS Code so AI agents can search and install Cult UI components.
Updated
The shadcn MCP server lets your editor's AI agent search the Cult UI registry, read component examples, and install components into your project. You ask in plain language, such as "add a prompt input from cult-ui to the chat page", and the agent runs the right shadcn add command.
List Cult UI in components.json
The MCP server only searches the registries listed in your project's components.json. The CLI adds Cult UI there the first time you run npx shadcn@latest add @cult-ui/<name>. If you have not added a component yet, add the entry yourself:
{
"registries": {
"@cult-ui": "https://www.cult-ui.com/r/{name}.json"
}
}The default @shadcn registry is always available and does not need an entry.
Connect your editor
Run the init command for your client from the project root:
pnpm dlx shadcn@latest mcp init --client cursor
This writes .cursor/mcp.json. Open Cursor Settings, then MCP, and enable the shadcn server. A green dot means it is connected.
To configure it by hand, add this server to your client's MCP config file:
{
"mcpServers": {
"shadcn": {
"command": "npx",
"args": ["shadcn@latest", "mcp"]
}
}
}Ask for components
Mention Cult UI by name so the agent searches the right registry:
- Show me the form controls in the cult-ui registry
- Add the Halo Select and Halo Switch from cult-ui to the settings page
- Build a pricing section using Halo Card and Border Beam Button from cult-ui
- Replace the chat input with Prompt Composer from cult-ui
Give the agent more context
The MCP server returns component source and examples, which is enough for most installs. For larger tasks, also point the agent at the docs written for LLMs, and add the Cult UI rules to your AGENTS.md. Both are on the LLMs & Agents page.