developer-tools

shadcn/ui Registry Manager

by reuvenaor

Manage and automate your React projects with shadcn/ui Registry Manager. Integrate shadcn UI components easily for smoot

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.

github stars

1

Docker containerized executionSupports custom registriesIncludes block components

best for

  • / React/Next.js developers using shadcn/ui components
  • / Automating project setup in CI/CD pipelines
  • / Managing shadcn projects in containerized environments
  • / AI agents building React applications

capabilities

  • / 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

what it does

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.

about

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

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.

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)
  • 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.

FAQ

What is the shadcn/ui Registry Manager MCP server?
shadcn/ui Registry Manager is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for shadcn/ui Registry Manager?
This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
MCP server reviews

Ratings

4.510 reviews
  • Shikha Mishra· Oct 10, 2024

    shadcn/ui Registry Manager is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Piyush G· Sep 9, 2024

    We evaluated shadcn/ui Registry Manager against two servers with overlapping tools; this profile had the clearer scope statement.

  • Chaitanya Patil· Aug 8, 2024

    Useful MCP listing: shadcn/ui Registry Manager is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Sakshi Patil· Jul 7, 2024

    shadcn/ui Registry Manager reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Ganesh Mohane· Jun 6, 2024

    I recommend shadcn/ui Registry Manager for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Oshnikdeep· May 5, 2024

    Strong directory entry: shadcn/ui Registry Manager surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Dhruvi Jain· Apr 4, 2024

    shadcn/ui Registry Manager has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Rahul Santra· Mar 3, 2024

    According to our notes, shadcn/ui Registry Manager benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Pratham Ware· Feb 2, 2024

    We wired shadcn/ui Registry Manager into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Yash Thakker· Jan 1, 2024

    shadcn/ui Registry Manager is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.