shadcn MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging (set to 'true' to enable) | |
| NODE_ENV | No | Set environment (e.g., 'development' or 'production') | |
| GITHUB_TOKEN | No | GitHub personal access token for higher rate limits (optional but recommended) |
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 |
|---|---|
| get_componentB | Get the source code and metadata for a specific shadcn/ui component |
| list_componentsC | List all available shadcn/ui components |
| get_blockB | Get a complete shadcn/ui block implementation |
| list_blocksA | List all available shadcn/ui blocks |
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 4 tools
Each tool has a unique purpose: listing vs getting, and blocks vs components. No overlap, clear boundaries.
All tools follow a consistent verb_noun pattern (get/list + block/component) with underscores, no style mixing.
4 tools are well-scoped for a reference server on shadcn/ui components and blocks, neither too few nor too many.
The set covers both listing and retrieving individual items for both blocks and components, meeting typical informational needs without obvious gaps.