@jpisnice/shadcn-ui-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | No | GitHub personal access token for higher rate limits (5000 requests/hour instead of 60) |
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
Each tool targets a distinct resource: theme, block, component, or directory structure. The get_component, get_component_demo, and get_component_metadata are clearly differentiated by what they return (source, demo, metadata). No tools overlap in purpose.
All tool names follow a consistent verb_noun pattern with snake_case: apply_theme, get_block, get_component, get_component_demo, get_component_metadata, get_directory_structure, get_theme, list_blocks, list_components, list_themes. No deviations or mixed conventions.
10 tools is well-scoped for a shadcn/ui reference server. It covers listing and retrieving components, blocks, and themes, plus applying a theme and fetching directory structure. Neither too sparse nor too heavy.
The tool surface fully covers the intended domain: components (list, get source, get demo, get metadata), blocks (list, get), themes (list, apply), and repository structure. There are no obvious gaps for a reference and theme-application server.