shadcn-registry-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHADCN_REGISTRY_URL | No | URL of a custom shadcn registry (e.g., internal design system). If not set, the official shadcn registry is used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_componentsA | List all available shadcn/ui components from the official registry |
| search_componentsA | Search for shadcn/ui components by name or description |
| get_component_infoA | Get detailed information about a shadcn/ui component including dependencies, files, and whether it is already installed in the current project |
| add_componentA | Install one or more shadcn/ui components into the current project. Automatically resolves and installs all dependencies. Use dryRun=true to preview what would be installed without making changes. |
| remove_componentA | Remove one or more installed shadcn/ui components from the project by deleting their files |
| list_installedA | List all shadcn/ui components that are currently installed in the project |
| list_groupsA | List all available component groups for bulk installation (e.g. "form", "overlay", "navigation") |
| detect_projectA | Detect the current project configuration: framework, package manager, component paths, and shadcn setup |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a clearly distinct operation: discovery, search, detailed info, add, remove, installed listing, groups, and project detection. There is no meaningful overlap that would confuse an agent.
All tool names follow a consistent verb_noun snake_case pattern such as list_components, add_component, and detect_project. The names are predictable and readable.
With 8 tools, the server is well-scoped for managing shadcn/ui registry components and project integration. Each tool serves a necessary function without redundancy.
The surface covers discovery, inspection, installation, removal, installed tracking, grouping, and project detection. The only notable gap is an explicit update/upgrade operation for already installed components.