Shadcn UI v4 MCP Server

What it does

This server gives a coding assistant direct access to the shadcn/ui v4 component library and its ports to other frameworks. It pulls component source code, example usage, dependency metadata and full blocks (multi-component layouts such as dashboards, calendars and forms) from the libraries' GitHub repositories, so the assistant writes UI code against the current components instead of guessing from memory.

One framework is served per running instance, picked with the --framework flag: React (shadcn/ui, the default), Svelte (shadcn-svelte), Vue (shadcn-vue) or React Native (react-native-reusables). For React you can also choose Radix UI (default) or Base UI as the primitive library with --ui-library or UI_LIBRARY.

Beyond lookups it carries three theme tools built on tweakcn presets: list the presets, inspect one, and apply one, which writes Tailwind/CSS theme code into your project (a dryRun option previews the change first, and a backup of the overwritten file may be made).

It runs over stdio by default, and can also serve stateless Streamable HTTP at a /mcp endpoint (or both at once) for shared or containerised setups; the repository includes Docker Compose files and a .mcpb bundle for one-click install in Claude Desktop. The old SSE transport has been removed; --mode sse is kept only as a deprecated alias for http.

What it needs

Node.js 20 or later (run through npx or bunx, or built from source with npm or pnpm). Network access to GitHub. A GitHub personal access token is optional but recommended: without one the server is held to GitHub's 60 requests an hour, with one it gets 5,000; the token needs no scopes. Docker is needed only for the container route, which builds its image locally.

Limits

Without a GitHub token it is limited to about 60 GitHub API requests an hour, which a few component lookups can use up. Each instance serves one framework at a time; switching means restarting with a different --framework value. The Base UI option applies to React only. Content comes from the upstream community repositories, so what is available for Svelte, Vue and React Native depends on those projects. The SSE transport is gone; clients must use stdio or Streamable HTTP.

Who it suits

Suits developers building with shadcn/ui or one of its Svelte, Vue or React Native ports who want an assistant to work from the real component code and examples. It runs on your own machine, needs no account, and apart from apply_theme only reads public GitHub content. It is a community project, not published by shadcn; anyone wanting the library makers' own tooling should look at what shadcn/ui ships itself. Teams wanting one shared instance can use the HTTP mode with Docker. Skip it if you do not use shadcn-style components.