How do I use shadcndashboard-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@shadcndashboard-mcp List all available dashboard blocks" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

shadcndashboard-mcp

by shadcnspace

Overview Schema Related Servers Score Discussions

JavaScript

Local

shadcndashboard-mcp

Official Model Context Protocol (MCP) server for Shadcn Dashboard.

This MCP server allows AI-powered IDEs and agents to discover, search, and install Shadcn Dashboard UI blocks directly into your projects — no copy-paste required.

Install MCP configuration

npx shadcndashboard-cli install <client>

Supported Clients

cursor
windsurf
claude
cline
antigravity

Related MCP server: aceternity-mcp

Manual Installation

Add to your IDE's MCP config:

{
  "mcpServers": {
    "shadcndashboard-mcp": {
      "command": "npx",
      "args": ["-y", "shadcndashboard-mcp@latest"]
    }
  }
}

For MCP, visit its MAIN PAGE For more information visit our documentation of How to use MCP Server

Available Tools

The server provides the following tools callable via MCP:

Tool Name	Description
`listBlocks`	Provides a comprehensive list of all Shadcn Dashboard blocks.
`listComponents`	Provides a comprehensive list of all Shadcn Dashboard components.
`getBlockInstall`	Returns the official installation command for a specific Shadcn Dashboard block.
`searchBlocks`	Search Shadcn Dashboard blocks using keywords or tags.
`listInstalledBlocks`	Lists all blocks that are currently installed in the project and get their files.
`get_audit_checklist`	Returns strict workflow rules and guidelines for agents interacting with this MCP server.

Note: Some blocks are PRO components, so you will need a valid license key to install and use them.

Available Prompts

The server provides the following prompts callable via MCP:

Prompt/Command	Description
`search`	Find specific UI block by name.
`create-ui`	Create a new UI layout using existing blocks.
`customization-guidelines`	Defines which parts of installed blocks can be safely modified.

Example Usage

Once configured, you can ask questions like:

"List all available dashboard blocks"

"Give me the installation command for the sidebar-01 block"

"Create a dashboard layout with a sidebar, a stats grid, and a data table."

"Search for chart blocks"

"Install the analytics-dashboard-01 block into my project"

Agent Instructions (Claude / Cursor / Windsurf)

If you are using Claude Projects, Cursor, or Windsurf, we have prepared a set of instructions you can copy-paste to make your AI use this MCP Server flawlessly. See claude-instructions.md.

Credits

Created by shadcndashboard.

MIT

Available Tools

6 tools

get_audit_checklistGet Agent Skills & InstructionsA

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It mentions returning rules but does not disclose whether it is read-only, idempotent, or has any side effects, lacking behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each essential. Front-loaded with 'CRITICAL' urgency, then states purpose and mandates usage. No superfluous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists; description mentions 'strict workflow rules and guidelines' but does not specify the format (e.g., list, structured data, plain text), leaving some ambiguity about the return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has zero parameters, and schema coverage is 100%. Description adds value by explaining the tool's purpose and content, achieving the baseline of 4 for no-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns 'strict workflow rules and guidelines' and emphasizes it must be executed before any other tools, distinguishing it from sibling block manipulation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs agents to execute this tool first before using any other tools in the MCP server, providing clear when-to-use guidance but not discussing when not to use or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

getBlockInstallGet Block Installation CommandA

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.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	The exact name of the block, e.g., 'sidebar-01'.

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It states the tool returns a command, but does not disclose behavioral traits such as side effects, authentication needs, or error handling. Adequate for a simple query but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loading the key action and resource, with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is fairly complete, providing purpose and usage context. Could potentially mention the output format or how to use the command.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description does not add meaning beyond what the input schema provides (exact block name). Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns the official installation command for a specific Shadcn Dashboard block, using a specific verb and resource, and distinguishes it from sibling tools like searchBlocks and listBlocks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that agents can use this tool to add a block before customizing it, implying a use case, but does not provide explicit when-not-to-use guidance or name alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

listBlocksList All BlocksA

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states the tool lists blocks, omitting details like performance, scope, or response structure, which is insufficient for a tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, no filler, front-loaded with key information. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the tool is simple (0 params), the description lacks detail on what information the list returns (e.g., names, descriptions), and there is no output schema to compensate. It adequately covers purpose but not return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so baseline is 4. The description adds value by explaining the purpose of the returned list (exploring block types), beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides a complete list of all Shadcn Dashboard blocks, using specific verb 'provides' and resource 'blocks'. It distinguishes from siblings like searchBlocks and listInstalledBlocks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives context to explore available block types before adding/customizing, but does not explicitly mention when not to use or alternatives like searchBlocks for targeted search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

listComponentsList All ComponentsB

Provides a full list of Shadcn Dashboard components. Agents can use this to discover components to build sections within a project.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. Only states it 'provides a full list', but does not disclose whether it is read-only, the response format, or any potential side effects. Minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no superfluous text. Front-loaded with purpose in first sentence and usage in second. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple list tool with no parameters, but lacks detail about the return format (e.g., component names, IDs) since there is no output schema. Could be improved by describing the structure of the list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. The description adds the nuance of a 'full list', which is consistent. For a zero-parameter tool, baseline is 4, and description meets it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it provides a full list of Shadcn Dashboard components, which is specific and actionable. However, it does not explicitly distinguish from sibling tool 'listBlocks' which may have overlapping functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for discovering components to build sections, but provides no guidance on when to use this tool versus alternatives like searchBlocks or listInstalledBlocks. No exclusions or context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

listInstalledBlocksList Installed BlocksA

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.

ParametersJSON Schema

Name	Required	Description	Default
`names`	No	Optional list of block names to filter the installed blocks.

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only states the basic operation without disclosing behavioral traits such as read-only nature, performance considerations, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words, front-loaded with the core purpose. Efficient and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one optional parameter, but the description omits return value details and behavioral context. It is minimally complete for a straightforward listing operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear parameter description in the schema. The description restates the filter option but adds no new semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists currently installed blocks, which differentiates it from sibling tools like listBlocks (which may list all blocks) and getBlockInstall (which gets a single install).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: agents can use it to determine available blocks for customization or updating. It does not explicitly exclude alternatives but implies a specific use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

searchBlocksSearch Blocks by KeywordA

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.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Keyword or tag to search for relevant blocks.

TDQS

A3.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must fully convey behavior. Only states it searches by keywords/tags, but omits details like search algorithm, result ordering, pagination, or case sensitivity. Insufficient for a new agent to predict behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with no redundant information. Front-loaded with the core action; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given low complexity (one required parameter, no output schema, no nested objects), the description covers the essential use. Lacks some details about result format, but is complete enough for a simple search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single 'query' parameter described as 'Keyword or tag to search for relevant blocks.' Schema coverage is 100%, and description adds no extra meaning beyond the schema's description. Baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it searches blocks by keywords or tags. Distinguishes from sibling tools like listBlocks (listing all) and getBlockInstall (installation details).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear usage scenario: finding relevant blocks when building a page based on user requirements or content type. Does not explicitly state when not to use or mention alternatives, but context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

6 tool updatesv1.0.0Jul 29, 2026
- First observedget_audit_checklist
- First observedgetBlockInstall
- First observedlistBlocks
- First observedlistComponents
- First observedlistInstalledBlocks
- First observedsearchBlocks

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0

Disambiguation4/5

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.

Naming Consistency2/5

Inconsistent naming: most use camelCase (getBlockInstall, searchBlocks, etc.) but get_audit_checklist uses snake_case. This breaks the pattern.

Tool Count4/5

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.

Completeness3/5

Covers core discovery and installation but lacks tools for updating, removing, or getting details of specific components. The checklist tool is a unique prerequisite.

Maintenance

ActivityMaintained

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

ClawLinkOAuth
dev.claw-link
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
App Automation Workplace & Productivity
24
Figma MCP ServerOAuth
com.figma.mcp
The Figma MCP server brings Figma design context directly into your AI workflow.
Developer Tools Content Management Systems
31,960
anotherai
dev.anotherai
MCP server for building and testing AI agents with multi-model experimentation and insights.
Agent Orchestration Autonomous Agents Testing & QA Tools
2
microservices.sh
sh.microservices
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Cloud Platforms Agent Orchestration Developer Tools
21

Related MCP Servers

Shadcn UI MCP Server
Developer Tools Content Management Systems
heilgar
A
license
C
quality
D
maintenance
A Model Control Protocol server that allows users to discover, install, and manage Shadcn UI components and blocks through natural language interactions in compatible AI tools.
Updated a year ago (2025-05-21 16:34 UTC)
6
367
25
MIT
aceternity-mcp
Developer Tools Design Tools
devinoldenburg
A
license
A
quality
A
maintenance
MCP server for Aceternity UI components, enabling AI assistants to discover, search, install, and generate page layouts with 106 components.
Updated 4 months ago (2026-05-13 21:41 UTC)
12
1
MIT
aceternityui-mcp
Developer Tools Design Tools
rudra016
A
license
A
quality
F
maintenance
An MCP server that enables AI assistants to search, discover, and install Aceternity UI components programmatically.
Updated a year ago (2025-07-19 07:39 UTC)
5
375
23
MIT
shadcn
Developer Tools Design Tools
dealenx
A
license
Not graded
quality
D
maintenance
This MCP server provides tools to install and manage shadcn/ui components directly from AI coding agents.
Updated 6 months ago (2026-02-22 23:18 UTC)
2
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shadcnspace/shadcndashboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server