MCP server for shadcn/ui component references
Shadcn Ui becomes available to MCP clients through the shadcn ui mcp server. MCP server for shadcn/ui component references.
A powerful and flexible MCP (Model Control Protocol) server designed to enhance the development experience with Shadcn UI components. This server provides a robust foundation for building and managing UI components with advanced tooling and functionality.
Once connected, the assistant can call these 10 tools directly:
list-components — Get the list of available shadcn/ui componentsget-component-docs — Get documentation for a specific componentinstall-component — Install a shadcn/ui componentlist-blocks — Get the list of available shadcn/ui blocksget-block-docs — Get documentation for a specific blockinstall-blocks — Install a shadcn/ui blockTools — The MCP server provides a set of tools that can be used through the Model Control Protocol:Functionality — The Functionality tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverDebugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Knowledge and memory servers address the most frustrating trait of language models — walking into every conversation with no recollection of the last one. Shadcn Ui sits in that group, and the shape of its toolset — list-components, get-component-docs, install-component among others — tells you what it is really for. Worth comparing against the other knowledge memory servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| list-components | Get the list of available shadcn/ui components |
| get-component-docs | Get documentation for a specific component |
| install-component | Install a shadcn/ui component |
| list-blocks | Get the list of available shadcn/ui blocks |
| get-block-docs | Get documentation for a specific block |
| install-blocks | Install a shadcn/ui block |
| Tools | The MCP server provides a set of tools that can be used through the Model Control Protocol: |
| Functionality | The Functionality tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) for debugging: |
{
"mcpServers": {
"shadcn-ui-server": {
"command": "npx",
"args": ["@heilgar/shadcn-ui-mcp-server"]
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.