shadcn/ui in Claude Desktop
Add shadcn.io under Customize → Connectors and Claude can plan pages from our blocks, pick icons from your set and give you the install, in Chat or in a Cowork folder. Any Claude plan works; you just need shadcn.io Pro.
- Kind
- App
- Goes in
Settings → Connectors- Connects
- Over HTTP
- Team config
- No
Add it as a custom connector
Claude Desktop reaches the server from Anthropic's cloud, so there's nothing to install on your computer. Signed in with Pro, the name and URL beside the steps already carry your token.
Copy the name and URL
The box holds the name,
shadcnio, and your MCP URL with the token in its?token=part. No token yet? Create one on your account.Open Customize → Connectors
Click Customize in the sidebar, then Connectors (Settings → Connectors lists the same ones). Click Add, then Add custom connector.
Paste the URL and add it
Enter
shadcnioas the name and paste the URL whole: the token inside it is the credential, with no OAuth sign-in to set up. Click Add, and it shows Connected under Your connectors.Turn it on in a chat
In a new chat, click + at the bottom left, open Connectors and switch
shadcnioon. Name it in your first prompts (use shadcnio…) so Claude reaches for it.
How it reads, with YOUR_TOKEN where your token goes:
Name: shadcnio URL: https://www.shadcn.io/api/mcp?token=YOUR_TOKEN
The connector is saved to your Claude account, not to this computer. Anyone holding the URL can spend your Pro: if it leaks, regenerate the token and add the connector again.
| Route | Who adds it | Where it works |
|---|---|---|
| Custom connector | You, in Customize → Connectors (Free, Pro, Max) | Chat, Cowork, claude.ai and the mobile apps |
| Organization connector | An Owner, in Organization settings → Connectors (Team, Enterprise) | Every member, through one shared URL |
claude_desktop_config.json | You, in Settings → Developer → Edit Config, through mcp-remote | This computer's desktop app only, after a restart |
Check Claude sees it
Customize → Connectors lists shadcnio under Your connectors, marked Connected, and its page shows each tool under Tool permissions.
- Open Customize → Connectors and select
shadcnio: Tool permissions lists its 22 tools. - Start a new chat, click +, open Connectors and check
shadcniois switched on. - Send the prompt below and allow
whoamiwhen Claude asks to use it, and the reply names your account and the calls left this minute.
Three chats in Claude Desktop
Planning and icons in Chat, then files in Cowork: the prompt, the calls Claude makes and what you end up with. Switch a tab's connector off to see what Claude writes from its training alone.
- shadcn.io MCP connected · 22 tools
MCP call: plan_page({ brief: "launch page for a habit tracker with a free and a pro plan", sections: ["hero", "features", "pricing", "faq"] })Returns: Four sections, a pick and two alternatives eachMCP call: search_blocks({ query: "free plan next to a pro plan", category: "pricing" })Returns: pricing-free-vs-pro, closer to the briefMCP call: get_block({ names: ["hero-centered-email-capture", "features-bento-grid", "pricing-free-vs-pro", "faq-accordion"], include: ["install", "preview"] })Returns: One shadcn add for the four, and their previewsAgent step: Wrote the copy for each sectionReturns: Headline, features, two plans and the questions
In your project
Launch page
- Four real blocks, each with a preview
- One command to paste in your project
1 prompt → 3 MCP calls
Things to ask Claude
Each one names the server and states the stack, since a chat can't open your project the way an editor does.
Make Claude reach for it
The settings in Claude that decide when it calls the server, what it asks you first and where its answers land.
Always allow the read-only tools
Every shadcnio tool only reads. Open
shadcnioin Customize → Connectors and set its tools to Always allow under Tool permissions: chats stop pausing for each call.Keep it loaded among many connectors
On Auto or On demand, Claude may skip loading
shadcniountil it searches for a connector. For a chat about UI, open + → Connectors → Tool access and pick Always available; it applies to that conversation only.Say your stack once, in a Project
Set a Project's instructions to your stack and one rule, and every chat in that Project starts from them, so you never restate your framework.
We build with Next.js, React on Base UI and pnpm. For UI, use the shadcnio connector: search before writing a component, and give me its install command.
Let Cowork write the files
Chat can't write to your disk, but Cowork works in a folder you connect. Ask there, and Claude saves the files
get_install_planreturns straight into your project.Your own token, from the config file
Where no connector can carry your own token, as on a Claude Team plan, add it locally under Settings → Developer → Edit Config through
mcp-remote(it needs Node), then quit and reopen Claude.{ "mcpServers": { "shadcnio": { "command": "npx", "args": ["-y", "mcp-remote", "YOUR_MCP_URL"] } } }
The same connector in the Code tab
Connectors follow your Claude account, so the Code tab, and Claude Code signed in with the same account, see
shadcnioas well, and there Claude runs the install itself. More in the Claude Code guide.
Fixes for Claude Desktop
What you see in Claude, and the fix. For errors every client shares, read the troubleshooting guide.
- Adding it ends in Couldn't reach the MCP server, or a sign-in page that fails.
- The token in the URL is missing, cut off or old, so the server answers 401 and Claude goes looking for a sign-in that doesn't exist. Copy the URL again from your MCP page and add the connector with it whole.
- Calls to shadcnio fail after you regenerated your token.
- The connector still holds the previous URL, and the server rejects it with 401. Remove
shadcnioin Customize → Connectors and add it again with the new one. - Every call fails with 403, even with a fresh URL.
- Claude gets through and the token checks out, but Pro has ended on the shadcn.io account it belongs to. Renew it and the connector works again as it stands: nothing to remove or re-add.
- Claude answers from memory and never calls shadcnio.
- The connector toggle under + → Connectors is per conversation: check it's on. Then name the server in the prompt, or set Tool access to Always available for that chat.
- Your Team plan's Connectors page has no way to add a custom connector.
- On Team and Enterprise, only Owners add connectors, in Organization settings → Connectors. Ask one, or use the config file on your own machine with your own token.
- A server added to
claude_desktop_config.jsonnever appears. - Claude reads the file at startup only: quit it completely, since closing the window isn't enough, and reopen it. Still missing?
mcp.login~/Library/Logs/Claude(macOS) or%APPDATA%\Claude\logs(Windows) says why, often a JSON typo or no Node fornpx.
Get the MCP for Claude Desktop with Pro
The MCP comes with every Pro plan, with every block and premium template, for you or your whole team. Monthly, yearly or lifetime.
4.9/5 out of 5 · 150+ reviewsfrom 150+ founders and developers.
- Secure checkout via Stripe
- Code lives in your repo
- Keep what you've shipped if you cancel
- License terms
Frequently asked questions
The shadcn MCP in Claude Desktop: setup, limits, and the rest.
No. Claude reaches remote connectors from Anthropic's cloud, even inside the desktop app, so nothing is installed locally and Node isn't needed. The only route that runs on your machine is claude_desktop_config.json with mcp-remote.
Yes. A connector belongs to your Claude account, so the one you add in the desktop app is there in the browser and in the iOS and Android apps once you sign in. Switch it on per chat from the + menu.
Yes, with mcp-remote, which needs Node. Open Settings, Developer, Edit Config, add a shadcnio entry that runs npx -y mcp-remote with your MCP URL, then quit Claude completely and reopen it. That route works on this computer's desktop app only.
Pasted docs are a single page, frozen when you copied it, and they eat into the conversation. The connector looks up only what the task needs, across every component, 6,231 blocks and 294k icons, and returns installs for your framework with your token already in them.
Chat has no shell on your computer, so Claude hands you the command, token included, to paste in your project's terminal. In Cowork it can write the files into a folder you connect, and in the Code tab it can run the command itself.
Pick Allow always when Claude asks, or open the connector in Customize, Connectors and set its tools to Always allow under Tool permissions. Every tool on the server only reads the registry, so none of them changes your files or your accounts.
Tell it. Say React, Vue, Svelte or Solid, and for React whether you're on Base UI, Ark UI, Radix or React Aria; with nothing said, the tools answer for React on Base UI. A Project's instructions can state it once for every chat inside it.
Yes. Hover shadcnio under + then Connectors to see its seven prompts (add, block, form, setup, page, icons and design) and its resources, then attach one to your message: a brand's DESIGN.md, or a guide on forms, styling, colors or RTL.
On Auto or On demand, Claude may not load shadcnio until it searches for a connector. For a chat about UI, open + then Connectors then Tool access and pick Always available. It applies to that conversation only.
No. You add a custom connector yourself on Free, Pro and Max, and an Owner adds it on Team and Enterprise. What the server itself needs is a shadcn.io Pro plan on the account behind your token.
The one in the URL the Owner entered, so every member's calls count against that single account and its 600 requests a minute. For each person to use their own Pro, add the server on each machine through claude_desktop_config.json instead, where your organization allows local servers.
On Team and Enterprise, only Owners add connectors, in Organization settings, Connectors. Ask an Owner, or use the config file on your own machine with your own token.
It sits in the connector's URL, saved with your Claude account, and Claude sends it only to the shadcn.io server. Treat that URL like a password: keep it out of chats and screenshots, and if it leaks, regenerate the token on your account page and re-add the connector.
Only the tool calls: their names and inputs, such as a component name or a framework. Your conversation and files stay with Claude and on your machine, and every tool only reads the registry.
The token in the URL is missing, cut off or old, so the server answers 401 and Claude goes looking for a sign-in that doesn't exist. Copy the URL again from your MCP page and add the connector with it whole.
After you regenerate the token the connector still holds the old URL and gets 401: remove shadcnio and add it again. A 403 means Pro has ended on the account; renew it and the connector works as it stands. Past 600 calls a minute you get a 429.
Claude reads the file at startup only, so quit it completely, since closing the window isn't enough, and reopen it. If it's still missing, mcp.log in the Claude logs folder says why, often a JSON typo or no Node for npx.
Using another agent too?
The same URL works in every MCP client: use it beside Claude Desktop, in your editor, your terminal or your chat app.
4.9 out of 5 from 150+ developers
Put the registry in Claude's chats
One custom connector brings every component, 6,231 blocks and 294k icons into Chat and Cowork, with any shadcn.io Pro plan.
Get Pro