
Shadcn Registry manager
MCP server for Shadcn UI, enabling automated, remote, or containerized project management via local or remote registries
README
shadcn registry manager - MCP Server
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.
What It Does
This MCP server exposes shadcn CLI operations as MCP tools, so you (or an AI agent) can:
- Initialize a project
- Add components from the shadcn registry including block components
- List and fetch registry items
- Run all shadcn CLI workflows remotely
- Supports both the official shadcn registry - https://ui.shadcn.com/r and custom/self-hosted registries follow this guide: https://ui.shadcn.com/docs/blocks
Usage
Docker
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"
],
},
Docker mounting explanation:
-
<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)
Docker ENV Variables:
- REGISTRY_URL
- option 1:
https://ui.shadcn.com/r
- The URL of the shadcn registry - option 2:
http://localhost:3000>/r
- The URL of your own registry server (follow this guide: https://ui.shadcn.com/docs/blocks)
- option 1:
- STYLE - is the style of the shadcn registry -
new-york
npx
You 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"
}
}
Claude
You can also use the MCP server with Claude. Here are the configuration options:
Claude CLI Command:
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
Claude .mcp.json Configuration:
{
"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"
}
}
}
npx ENV Variables:
- WORKSPACE_DIR - The path to your project directory (mounted as the workspace)
- REGISTRY_URL
- option 1:
https://ui.shadcn.com/r
- The URL of the shadcn registry - option 2:
http://localhost:3000/r
- The URL of your own registry server (follow this guide: https://ui.shadcn.com/docs/blocks)
- option 1:
- STYLE - is the style of the shadcn registry -
new-york
Example MCP Tools
get_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 registry
Example Usage
use the tool `get_blocks` to get the blocks from the registry
use the tool `add_item` - dashboard-01 to your project
Source
made with ❤️ by Reuven Naor
MIT License. See LICENSE for details.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.