shadcn/ui Registry Manager

shadcn/ui Registry Manager

reuvenaor

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.

Integrates with the shadcn/ui component registry to initialize projects, add components, and manage configurations remotely through CLI operations like init and add, supporting both official and custom registries for automating React/Next.js project setup and component library management.

1421 views1Local (stdio)

What it does

  • Initialize shadcn/ui projects with configurations
  • Add UI components from shadcn registry
  • List available registry components and blocks
  • Execute shadcn CLI commands remotely
  • Connect to custom or self-hosted registries
  • Manage project configurations programmatically

Best for

React/Next.js developers using shadcn/ui componentsAutomating project setup in CI/CD pipelinesManaging shadcn projects in containerized environmentsAI agents building React applications
Docker containerized executionSupports custom registriesIncludes block components

About shadcn/ui Registry Manager

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.

How to install

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.

License

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.

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)
  • 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)
  • STYLE - is the style of the shadcn registry - new-york

Example MCP Tools

  • get_init_instructions: Get project initialization instructions
  • execute_init: Run full project initialization
  • get_items: List available registry items
  • get_item: Fetch a specific registry item
  • add_item: Add a registry item to your project
  • execute_add: Add multiple components to your project
  • get_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.

Alternatives

Related Skills

Browse all skills
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

18
mcp-manager

Manage MCP (Model Context Protocol) servers in Claude Code projects. Use this skill when the user requests enabling, installing, disabling, or removing specific MCP servers like context7 or chrome-devtools. Always operates at project level (local scope only).

7
ai-sdk

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

6
api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

4
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

4
cli-builder

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

3