The shadcn MCP server for AI coding agents
DesignRevision MCP is a shadcn MCP server that gives Claude Code, Cursor, Codex, and any MCP agent live access to real shadcn/ui components. Your agent searches the registry, inspects a component, and installs it — dependencies already resolved — instead of guessing markup from memory.
Illustrative — a real tool-call sequence.
Works with the AI agents you already use
One remote MCP endpoint, connected to every major coding agent. Five have step-by-step setup guides today, with more shipping.
What is a shadcn MCP server?
A shadcn MCP server is a tool server that connects an AI coding agent to a shadcn/ui component library over the Model Context Protocol (MCP) — the open standard agents use to call external tools. Instead of writing components from memory, the agent queries the server for real, up-to-date shadcn/ui code.
DesignRevision MCP is that server. It exposes 12 tools your agent can call — to search the registry, read a component's real source, and get a ready-to-run install command — over a single remote endpoint, authenticated with a token. It works with Claude Code, Cursor, Codex, Windsurf, Claude Desktop, and any MCP-capable client.
The result: your agent installs the exact component you asked for, with its dependencies resolved, instead of hallucinating markup that looks close but doesn't compile.
From prompt to installed component
Ask your agent for a component. It calls DesignRevision MCP, gets the real thing, and installs it — no copy-pasting from a docs site.
Your agent searches the registry
Tools like search_items and list_popular find the right shadcn/ui component or block for the task.
It pulls the real source
get_item_source and get_item_details return the actual component code, props, and dependencies — not a hallucinated approximation.
And installs it in your project
get_install_command hands back a ready-to-run command, so the component lands in your codebase correctly the first time.
12 tools, three jobs
Every tool your agent can call, named and documented — not a vague "15 tools" with three examples.
Discovery
search_itemsSearch components & blocks by keywordlist_itemsBrowse the full cataloglist_popularThe most-used componentslist_block_categoriesAll block categorieslist_blocks_in_categoryBlocks within a category
Retrieval
get_itemFetch a component by nameget_item_detailsProps, variants & metadataget_item_sourceThe real component sourceget_preview_urlA live preview linkget_install_commandReady-to-run install command
Utility
whoamiYour account & planget_registry_statsRegistry size & coverage
See every parameter and return shape in the full tools reference.
Free to start — credits only when you pull
Browsing and searching the registry is cheap or free. You only spend credits when you pull a full component's source. No subscription wall before you've seen what you're paying for.
Solomore credits
Teamshared workspace
Businessunlimited scale
No card required to start.
The shadcn MCP server vs. the alternatives
An honest look at how DesignRevision MCP compares — the comparison none of the others will show you.
| DesignRevision MCP | shadcn official MCP | shadcn.io | Shadcn Studio | |
|---|---|---|---|---|
| Free to start (no subscription) | ✓ | ✓ | — | — |
| Freemium, credit-metered | ✓ | n/a | — | — |
| Every tool named & documented | ✓ | ✓ | — | — |
| Curated component registry | ✓ | — | ✓ | ✓ |
| Per-agent setup guides | ✓ | ✓ | ✓ | partial |
| Acknowledges the alternatives | ✓ | — | — | — |
Feature comparison as of July 2026. Built on the same Model Context Protocol as shadcn's official MCP server.
Add it to your agent in one line
Connect the remote endpoint with your token. Here's Claude Code — every agent has a guide.
claude mcp add --transport http design-revision https://mcp.designrevision.com/mcp --header "Authorization: Bearer YOUR_TOKEN"Still deciding? See the best MCP servers for Claude Code.
Frequently asked questions
-
-
DesignRevision MCP is a Model Context Protocol (MCP) server that gives your AI coding agent live access to real shadcn/ui components. Instead of writing markup from memory, the agent searches a registry, inspects a component, and installs it with the dependencies already resolved — over a single remote endpoint.
-
-
It works with Claude Code, Cursor, Codex, Windsurf, and Claude Desktop today — each with a step-by-step setup guide — plus any MCP-capable client (Perplexity, ChatGPT, JetBrains, and VS Code included). It is a standard remote MCP server, so if your tool speaks MCP, it connects.
-
-
Yes — it is free to start, with no card required. The free plan includes 500 credits a month. Browsing and searching the registry is cheap or free; credits are spent on full component-source pulls. Paid plans (Solo, Team, and Business) add more credits as you scale.
-
-
Twelve, grouped into three jobs: discovery (search and list components and blocks), retrieval (get a component, its source, a preview, or an install command), and utility (check your account and registry stats). Your agent calls them directly during a task.
-
-
It is built on the same Model Context Protocol, so it is compatible — but it adds a curated component registry, a transparent freemium credit model instead of a flat gate, honest comparisons to the alternatives, and documented support for more AI agents. The official MCP is a reference implementation; DesignRevision MCP is the product built on top of it.
-
-
In Claude Code, run a single claude mcp add command with the remote endpoint and your token. In Cursor, add it to .cursor/mcp.json with a serverUrl and an Authorization header. Both take under a minute — see the per-agent setup guides linked on this page.
Give your agent real shadcn/ui access
Stop shipping hallucinated markup. Connect DesignRevision MCP and install real components straight from your AI agent — free to start.