Shadcn UI v4 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host binding (default: 0.0.0.0) | |
| MCP_PORT | No | SSE server port (default: 7423 - SHADCN on keypad!) | |
| MCP_CORS_ORIGINS | No | CORS origins (comma-separated) | |
| MCP_TRANSPORT_MODE | No | Transport mode (stdio|sse|dual) | |
| GITHUB_PERSONAL_ACCESS_TOKEN | No | GitHub API token |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_componentA | Get the source code for a specific shadcn/ui v4 component |
| get_component_demoA | Get demo code illustrating how a shadcn/ui v4 component should be used |
| list_componentsB | Get all available shadcn/ui v4 components |
| get_component_metadataA | Get metadata for a specific shadcn/ui v4 component |
| get_directory_structureB | Get the directory structure of the shadcn-ui v4 repository |
| get_blockA | Get source code for a specific shadcn/ui v4 block (e.g., calendar-01, dashboard-01) |
| list_blocksB | Get all available shadcn/ui v4 blocks with categorization |
| apply_themeC | Apply a TweakCN theme preset to the project |
| list_themesA | List available tweakcn themes |
| get_themeB | Get details of a specific tweakcn theme |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build-shadcn-page | Generate a complete shadcn/ui page using v4 components and blocks |
| create-dashboard | Create a comprehensive dashboard using shadcn/ui v4 blocks and components |
| create-auth-flow | Generate authentication pages using shadcn/ui v4 login blocks |
| optimize-shadcn-component | Optimize or enhance existing shadcn/ui components with best practices |
| create-data-table | Create advanced data tables with shadcn/ui components |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_components | List of available shadcn/ui components that can be used in the project |
| get_theme_metadata | Returns metadata about the currently configured theme |
TDQS
Scored across 10 tools
Most tools target distinct resources (component, block, theme, repo structure) and actions (get, list, apply). However, get_component, get_component_demo, and get_component_metadata all relate to component details, which could cause slight confusion for an agent deciding which one to call.
Every tool name follows a consistent snake_case verb_noun pattern: get_component, list_components, apply_theme, etc. The prefixes (get_, list_, apply_) are used uniformly, making the set highly predictable.
With 10 tools, the surface is well-scoped for a UI component reference service. Each tool covers a distinct resource or operation without redundancy, fitting comfortably within the ideal 3–15 range.
The tools cover the core lifecycle: listing and fetching components, blocks, themes, demos, metadata, and applying themes. Minor gaps exist, such as no search/filter for components or blocks and no demo retrieval for blocks, but agents can work around these for the stated purpose.