shadcn/ui MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_componentsA | List all available shadcn/ui components with optional category filtering |
| get_component_sourceB | Get the source code for a specific shadcn/ui component |
| get_component_metadataA | Get metadata for a specific component including dependencies and description |
| get_component_demoB | Get demo code and usage examples for a specific component |
| install_componentB | Install one or more shadcn/ui components using the CLI |
| list_blocksB | List all available shadcn/ui blocks with optional category filtering |
| get_block_sourceB | Get the complete source code for a shadcn/ui block |
| install_blockB | Install a shadcn/ui block with all its dependencies |
| browse_repositoryC | Browse the shadcn/ui repository structure |
| search_repositoryC | Search for files or content in the shadcn/ui repository |
| init_shadcnB | Initialize shadcn/ui in a project |
| check_project_statusB | Check the current project status and shadcn/ui configuration |
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 12 tools
Each tool targets a distinct operation on specific entities: blocks vs components vs repository vs project init/status. No two tools have overlapping purposes, and descriptions clearly differentiate them.
All tool names follow a consistent snake_case verb_noun pattern (e.g., get_block_source, install_component, list_blocks). No mixing of conventions.
12 tools is well within the ideal range (3-15) for a focused server. Each tool serves a clear purpose without redundancy or bloat.
Covers init, listing, retrieval of source/demo/metadata, installation, and repository browsing/search. Minor gap: block metadata is missing (only component has metadata getter), but core workflows are fully supported.