shadcndashboard-mcp
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_audit_checklistA | CRITICAL: You MUST execute this tool BEFORE using any other tools in this MCP server. Returns the strict workflow rules and guidelines for agents interacting with Shadcn Dashboard. Agents MUST read this first to understand how to handle free vs PRO components, package managers, and installation flows. |
| listBlocksA | Provides a complete list of all Shadcn Dashboard blocks that can be used in a project. Agents can use this to explore available block types before deciding which ones to add or customize. |
| listComponentsB | Provides a full list of Shadcn Dashboard components. Agents can use this to discover components to build sections within a project. |
| getBlockInstallA | Returns the official installation command for a specific Shadcn Dashboard block. Agents can use this to add a block to the project automatically before customizing it. |
| searchBlocksA | Search Shadcn Dashboard blocks using keywords or tags. Agents can use this to find relevant blocks when building a page based on user requirements or content type. |
| listInstalledBlocksA | Lists all blocks that are currently installed in the project. Agents can use this to determine which blocks are available for customization or updating, and optionally filter by specific block names. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search | Search for a component to use in your project. |
| create-ui | Architect a full UI page using Shadcn Dashboard blocks. |
| customization-guidelines | Defines which parts of installed blocks can be safely modified (text only). Agents can read this before editing any block files. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Tools target distinct areas: blocks vs components, installed vs all, search vs list. Some slight overlap between listBlocks and searchBlocks, but descriptions clarify. get_audit_checklist is a prerequisite, not a functional overlap.
Inconsistent naming: most use camelCase (getBlockInstall, searchBlocks, etc.) but get_audit_checklist uses snake_case. This breaks the pattern.
6 tools for a dashboard block/component server is well-scoped: covers listing, searching, installing, and checking installed items. Not too many or too few.
Covers core discovery and installation but lacks tools for updating, removing, or getting details of specific components. The checklist tool is a unique prerequisite.