What can you do with this server?

The Shadcn Space MCP server enables AI-powered IDEs and agents to discover, search, install, and manage Shadcn Space UI blocks and pages directly in your projects. Blocks & Components * listBlocks – Get a complete list of all available Shadcn Space UI blocks. * listComponents – Get a full list of all available components. * searchBlocks – Search for blocks using keywords or tags. * getBlockInstall – Retrieve the official installation command for a specific block (e.g., hero-01). * listInstalledBlocks – List blocks already installed in the project, with optional filtering by name. Pages (PRO, requires license) * listPages – Get a complete list of all available Shadcn Space pages. * searchPages – Search pages using keywords or tags. * getPageInstall – Retrieve the installation command for a specific page. * listInstalledPages – List pages already installed in the project. Agent Guidance * get_audit_checklist – Returns strict workflow rules and guidelines for agents interacting with the server. * Prompts available: search (find a block by name), create-ui (generate new UI from existing blocks), and customization-guidelines (learn which parts of installed blocks can be safely modified).

de en es ja ko ru zh

Shadcn Space MCP

by shadcnspace

Overview Schema Related Servers Score Discussions

JavaScript

Hybrid

shadcnspace-mcp

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

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

Install MCP configuration

npx shadcnspace-cli install <client>

Supported Clients

cursor
windsurf
claude
cline
antigravity

Related MCP server: shadcn-vue-mcp

Manual Installation

Add to your IDE's MCP config:

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

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 shadcnspace blocks.
`listComponents`	Provides a comprehensive list of all shadcnspace components.
`getBlockInstall`	Returns the official installation command for a specific Shadcn Space block.
`searchBlocks`	Search Shadcn Space blocks using keywords or tags.
`listInstalledBlocks`	Lists all blocks that are currently installed in the project and get their files.
`listPages`	Provides a complete list of all Shadcn Space pages.
`getPageInstall`	Returns the official installation command for a specific Shadcn Space page.
`searchPages`	Search Shadcn Space pages using keywords or tags.
`listInstalledPages`	Lists all pages that are currently installed in the project.
`get_audit_checklist`	Returns strict workflow rules and guidelines for agents interacting with this MCP server.

Note: All pages are PRO components, so you will need to have 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 block using our exisitng 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 UI blocks"

"Give me the code for the accordion-01 component"

"Create a landing page for a coffee shop using a hero-01 block, a 3-column feature grid, and a dark-themed footer."

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 shadcnspace.

MIT

Available Tools

5 tools

getBlockInstallGet Block Installation CommandA

Returns the official installation command for a specific Shadcn Space 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., 'hero-01'.

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It states the tool is read-only (returns a command) and adds context about adding a block. It does not mention any side effects, permissions, or rate limits. For a simple read operation, this is adequate but not exceptional.

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 zero wasted words. The purpose is front-loaded in the first sentence, and usage context is in the second. Every sentence adds value.

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

Completeness5/5

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

Given the tool's simplicity (1 parameter, no output schema, no annotations, few siblings), the description fully covers what the tool does, when to use it, and what the parameter expects. No critical information is missing.

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 description coverage is 100% for the single parameter 'name', providing an example. The description adds 'for a specific Shadcn Space block' but no further details beyond the schema. Baseline is 3 due to full schema coverage.

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 it returns the installation command for a block and is used to add a block before customizing. The verb 'Returns' and resource 'installation command' are specific. It distinguishes from siblings such as listBlocks (listing) and listInstalledBlocks (listing installed) by focusing on the command retrieval action.

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 explicitly states when to use: 'Agents can use this to add a block to the project automatically before customizing it.' This provides clear usage context. However, it does not include when not to use or alternatives, though siblings implicitly cover other actions.

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 Space 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.8/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 only states 'complete list' but fails to disclose read-only nature, performance implications, 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 with no wasted words, directly stating purpose and typical usage context.

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?

For a simple listing tool with no output schema, the description adequately covers use case but could mention what fields are returned (e.g., block names/types).

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 baseline 4 applies. The description adds no param-specific info, but none is needed.

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 the tool lists all Shadcn Space blocks, distinguishing it from siblings like getBlockInstall or searchBlocks by focusing on exploration before addition/customization.

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 exploring available blocks before customizing, but does not explicitly contrast with siblings or state when not to use (e.g., if searching for a specific block, use searchBlocks).

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

listComponentsList All ComponentsA

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

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.7/5.0

Behavior3/5

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

Discloses it provides a 'full list', indicating a read-only operation. No annotations provided, so description covers basic behavior but lacks details on auth, rate limits, or return specifics.

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 front-loading the purpose. No redundant 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?

Adequate for a simple list tool with no parameters or output schema. Could mention return format (e.g., component names/details) but not critical.

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, so baseline 4 applies. Description adds no param info but schema coverage is complete; no additional meaning needed.

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 verb (list) and resource (components). Differentiates by focusing on 'components' rather than 'blocks', but does not explicitly distinguish from siblings like listBlocks.

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 pages/sections, but lacks explicit when-not-to-use or alternative tool mentions.

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

Behavior3/5

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

No annotations provided, description implies a read operation without side effects, but does not explicitly state safety or constraints. Adequate but not detailed.

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 short sentences covering function, purpose, and optional filter. No redundant information.

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?

Lacks details on output format or pagination, but given it's a list tool with no output schema, description is sufficient for basic use. Could be improved with return structure.

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 covers the only parameter fully; description adds 'optionally filter' which is already in schema. Minimal added value beyond 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?

Clearly states it lists installed blocks in the project, with ability to filter by name. Distinguishes from siblings like listBlocks (all blocks) and getBlockInstall (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 Guidelines3/5

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

Mentions use case for customization/updating but lacks explicit exclusion or comparison with sibling tools. Agent might need to infer when not to use.

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 Space 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.7/5.0

Behavior2/5

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

No annotations present, so description must fully disclose behavior. It does not state if the operation is read-only, any auth needs, rate limits, or return format. Only purpose is conveyed.

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, front-loaded with action and target. Every sentence adds value, no fluff.

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?

For a simple 1-param search tool with no output schema, description covers when to use but omits return value details (e.g., format, pagination). Adequate but not thorough.

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 single 'query' parameter described as 'Keyword or tag to search for relevant blocks.' Description repeats this but adds no significant new meaning beyond 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?

Description clearly states the tool searches Shadcn Space blocks using keywords or tags, with a specific use case. It distinguishes itself from siblings like listBlocks (all blocks) or search-related 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?

Explicit guidance on when to use: 'when building a page based on user requirements or content type.' No when-not or alternatives, but context is clear.

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.

5 tool updatesv1.2.3Apr 27, 2026
- 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.9/5.0

Disambiguation4/5

Tools have distinct purposes: listing all blocks, installed blocks, components, searching, and getting install commands. Slight potential confusion between listBlocks and listInstalledBlocks, but descriptions clarify the difference.

Naming Consistency4/5

All tools follow a verb+object pattern in camelCase (e.g., listBlocks, getBlockInstall). The pattern is consistent, though some names are multi-word (getBlockInstall) while others are two words (listBlocks).

Tool Count5/5

Five tools is well-scoped for a server focused on managing Shadcn Space blocks and components, providing essential discovery and installation information without being excessive.

Completeness4/5

Covers listing, searching, and install commands. Missing tools for adding/removing or customizing blocks, but the server's purpose appears informational, and agents can use the install command from getBlockInstall via shell.

Maintenance

ActivityStale

ResponsivenessNo issues

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

OpenRouter AFeaturedOAuth
ai.openrouter.mcp
The OpenRouter MCP server plugs OpenRouter into the AI tools you already use. Once connected, your assistant can pull live OpenRouter data (models, prices, your credits, rankings, and docs) and send quick test messages, all without leaving your editor.
AI & Machine Learning
221
Svelte MCP A
dev.svelte
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Developer Tools Documentation Access Code Analysis
42318
ArletOAuth
dev.arlet
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Developer Tools CI/CD & DevOps
2
neverinfamous-memory-journal-mcp
ai.smithery
A MCP server built for developers enabling Git based project management with project and personal…
Version Control Developer Tools Project Management
320

Related MCP Servers

@jpisnice/shadcn-ui-mcp-server
Developer Tools Code Analysis Documentation Access
Jpisnice
A
license
A
quality
D
maintenance
A mcp server to allow LLMS gain context about shadcn ui component structure,usage and installation
Updated 4 months ago (2026-05-16 13:09 UTC)
10
6,473
2,969
MIT
shadcn-vue-mcp
Developer Tools Autonomous Agents
HelloGGX
A
license
B
quality
D
maintenance
Shadcn-vue MCP Server is a powerful AI-driven tool that helps developers instantly create beautiful, modern UI components through natural language descriptions. It integrates the shadcn-vue component library and tailwindcss, seamlessly connects with mainstream IDEs, and provides a streamlined UI dev
Updated 10 months ago (2025-11-16 08:53 UTC)
5
225
108
Apache 2.0
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
shadcn-registry-mcp
Developer Tools Coding Agents
Rachidhssin
A
license
A
quality
C
maintenance
A secure MCP server that gives AI coding assistants direct access to the shadcn/ui registry, enabling fetching, installing, and wiring up components without switching context.
Updated 5 months ago (2026-03-24 09:15 UTC)
8
33
3
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/shadcnspace-mcp'

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