shadcn-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 |
|---|---|
| add_shadcn_componentC | Adds a shadcn component to the project workspace. |
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 1 tool
Only one tool exists, so there is no risk of confusion between tools. Disambiguation is perfect.
The single tool name follows a clear verb_noun pattern (add_shadcn_component) in snake_case, which is consistent and descriptive.
With only one tool, the server feels thin for a component management server. While the core operation is covered, additional tools for listing or removing components might be expected.
The server only supports adding a component, missing obvious operations like listing available components or removing them. This limits the agent's ability to manage shadcn components effectively.