MCP server
by reuvenaor
Manage and automate your React projects with shadcn/ui Registry Manager. Integrate shadcn UI components easily for smoot
Runs shadcn/ui CLI commands remotely to initialize React/Next.js projects and add UI components from the shadcn registry. Works with both official and custom component registries.
shadcn/ui Registry Manager is a community-built MCP server published by reuvenaor that provides AI assistants with tools and capabilities via the Model Context Protocol. Manage and automate your React projects with shadcn/ui Registry Manager. Integrate shadcn UI components easily for smoot It is categorized under developer tools.
You can install shadcn/ui Registry Manager in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
shadcn/ui Registry Manager is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired shadcn/ui Registry Manager into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
shadcn/ui Registry Manager has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, shadcn/ui Registry Manager benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
shadcn/ui Registry Manager is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, shadcn/ui Registry Manager benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
shadcn/ui Registry Manager is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired shadcn/ui Registry Manager into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
shadcn/ui Registry Manager has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We wired shadcn/ui Registry Manager into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
shadcn/ui Registry Manager is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 56
This project provides an MCP (Model Context Protocol) server for the shadcn/ui component registry and CLI. It enables remote, programmatic, or containerized execution of shadcn CLI commands (such as init, add, etc.) that you would normally run locally, making it easy to automate, integrate, or run in cloud/dev environments. The MCP server can connect to both local and remote shadcn registries, providing a secure, extensible, and technical interface for automating project management tasks via AI or CLI agents.
This MCP server exposes shadcn CLI operations as MCP tools, so you (or an AI agent) can:
Run the MCP server in a container, mounting your project directory:
Add the following to your mcp.json file:
"shadcn-registry-manager": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--mount",
"type=bind,src=<your-project-path>,dst=/workspace",
"-e",
"REGISTRY_URL=https://ui.shadcn.com/r",
"-e",
"STYLE=new-york",
"reuvenaor/shadcn-registry-manager"
],
},
<your-project-path> - Is the path to your project directory.
Example: /Library/Projects/shadcn-registry-manager/www
/workspace - is the path to the workspace directory inside the container.
(Don't change it, if you do, you must pass the same path as cwd param on every tool call)
https://ui.shadcn.com/r - The URL of the shadcn registryhttp://localhost:3000>/r - The URL of your own registry server (follow this guide: https://ui.shadcn.com/docs/blocks)new-yorkYou can also run the MCP server using npx, which is convenient for local development or CI/CD pipelines.
Add the following to your mcp.json file:
"shadcn-registry-manager": {
"command": "npx",
"args": [
"@reuvenorg/shadcn-registry-manager"
],
"env": {
"REGISTRY_URL": "https://ui.shadcn.com/r",
"WORKSPACE_DIR": "/Library/Projects/mcp-docker/www",
"STYLE": "new-york"
}
}
You can also use the MCP server with Claude. Here are the configuration options:
claude mcp add --scope project shadcn-registry-manager npx @reuvenorg/shadcn-registry-manager -e REGISTRY_URL=https://ui.shadcn.com/r -e WORKSPACE_DIR=/Library/Projects/resume -e STYLE=new-york
{
"shadcn-registry-manager": {
"type": "stdio",
"command": "npx",
"args": [
"@reuvenorg/shadcn-registry-manager"
],
"env": {
"REGISTRY_URL": "https://ui.shadcn.com/r",
"WORKSPACE_DIR": "/Library/Projects/resume",
"STYLE": "new-york"
}
}
}
https://ui.shadcn.com/r - The URL of the shadcn registryhttp://localhost:3000/r - The URL of your own registry server (follow this guide: https://ui.shadcn.com/docs/blocks)new-yorkget_init_instructions: Get project initialization instructionsexecute_init: Run full project initializationget_items: List available registry itemsget_item: Fetch a specific registry itemadd_item: Add a registry item to your projectexecute_add: Add multiple components to your projectget_blocks: Get current blocks from the registryuse the tool `get_blocks` to get the blocks from the registry
use the tool `add_item` - dashboard-01 to your project
made with ❤️ by Reuven Naor
MIT License. See LICENSE for details.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.