This server also ships inside UI UX Pro Max — a plugin that installs it already configured.

LABSCO SUMMARY

A read-only lookup desk for component registries, not an installer.

All seven of its tools only read and return text; when a component actually lands in your project, it is because your assistant went on to run the shadcn CLI itself, which happens outside this server. So nothing in your project changes until you run that command, and what the server hands back is a command rather than a file. One rough edge at package version 4.21.1: the full item listing prints [object Promise] where each item's add command should be, so the add command has to come from get_add_command_for_items, the tool that exists for it.

What it is

The shadcn command-line tool runs an MCP server as one of its subcommands, and that server is what this entry is — not the shadcn/ui component library that ships from the same repository. It connects an AI assistant to shadcn-compatible component registries; the vendor describes it as "a bridge between your AI assistant, component registries and the shadcn CLI." With it connected you ask for a component in plain language instead of reading the catalogue yourself and pasting code across.

What you get

Search across every registry the project has configured, by component name or by what the component does, plus a full item listing — the default shadcn/ui registry answers with 471 items.
The complete detail of any registry item: its name, description, type and the contents of its files.
Working demo code for an item — searching for something like accordion-demo returns the full implementation with its dependencies.
The shadcn CLI add command for one or more chosen items, handed back as text for your assistant to run.
A checklist to run over component code once it has been generated.
The names of the registries the current project is pointed at, including private and namespaced ones.
Seven tools in all, every one of them read-only: the server reads registries and returns text, and writes nothing into your project itself.

Requirements

Node with npx, and outbound network access to the registry. Nothing else — no account and no key, and no shadcn project either: the default shadcn/ui registry answered from an empty directory with no components.json in it, and the vendor states "No configuration is needed to access the standard shadcn/ui registry." A components.json entry is needed only to reach a second or namespaced registry, and a token in .env.local only when that registry is private.

Setup effort

One command — npx shadcn@latest mcp