get_component_details
Get detailed information about a specific shadcn/ui component
Get a shadcn/ui component's details and usage examples in the editor instead of switching to the docs site mid-build.
LABSCO SUMMARY
Two of the four tools take a component name and two help you find one, which covers both halves of the problem: recalling what the library has, and recalling how the thing you picked is used. Nothing here writes to your project — the server answers questions and the code stays yours to paste.
A lookup service for the shadcn/ui component library: four read-only tools that list the components, return one component's details, return its examples, and search by keyword.
npx on your PATH. No account, no key.
One command — npx -y shadcn-ui-mcp-server
USE CASES
Search by what you want it to do, read the details of the component that comes back, and take the usage examples straight into the file you are editing.
Before writing a component from scratch, list what already exists — the answer decides whether the next hour is spent building or installing.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_component_detailsGet detailed information about a specific shadcn/ui component
get_component_examplesGet usage examples for a specific shadcn/ui component
list_shadcn_componentsGet a list of all available shadcn/ui components
search_componentsSearch for shadcn/ui components by keyword
BEFORE YOU INSTALL
4 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"shadcn-ui-mcp-server": {
"command": "npx",
"args": [
"-y",
"shadcn-ui-mcp-server"
]
}
}
}npx -y shadcn-ui-mcp-server