Skip to content

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.

  1. 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.

  2. Open Customize → Connectors

    Click Customize in the sidebar, then Connectors (Settings → Connectors lists the same ones). Click Add, then Add custom connector.

  3. Paste the URL and add it

    Enter shadcnio as 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.

  4. Turn it on in a chat

    In a new chat, click + at the bottom left, open Connectors and switch shadcnio on. Name it in your first prompts (use shadcnio…) so Claude reaches for it.

Settings → Connectors
Sign in to get your config
Sign in with a Pro account, and this holds your MCP URL, ready to paste.

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.

Three ways to add it from Claude Desktop
RouteWho adds itWhere it works
Custom connectorYou, in Customize → Connectors (Free, Pro, Max)Chat, Cowork, claude.ai and the mobile apps
Organization connectorAn Owner, in Organization settings → Connectors (Team, Enterprise)Every member, through one shared URL
claude_desktop_config.jsonYou, in Settings → Developer → Edit Config, through mcp-remoteThis 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.

  1. Open Customize → Connectors and select shadcnio: Tool permissions lists its 22 tools.
  2. Start a new chat, click +, open Connectors and check shadcnio is switched on.
  3. Send the prompt below and allow whoami when Claude asks to use it, and the reply names your account and the calls left this minute.
Prompt
use shadcnio and tell me which shadcn.io account this connector belongs to

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.

Your agent
  1. shadcn.io MCP connected · 22 tools
  2. You: Plan a launch page for my habit tracker: hero, features, pricing and FAQ.
  3. 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 each
  4. MCP call: search_blocks({ query: "free plan next to a pro plan", category: "pricing" })Returns: pricing-free-vs-pro, closer to the brief
  5. MCP 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 previews
  6. Agent step: Wrote the copy for each sectionReturns: Headline, features, two plans and the questions
  7. Your agent: Here's the plan with a preview link per section, and one command that adds all four blocks to your project.

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.

01
use shadcnio to plan a landing page for my bakery's online ordering, with the menu and opening hours
02
use shadcnio to compare the date picker and the date input, and tell me which suits a birthday field
03
use shadcnio to write a signup form for my Vue app with email, password and a terms checkbox
04
use shadcnio to find a kanban board block for Svelte and give me its install command
05
use shadcnio to pick Phosphor icons for a music player's play, pause, skip and shuffle buttons
06
use shadcnio to read Headspace's DESIGN.md and turn its colors into light and dark theme variables
07
use shadcnio to list every file a Solid project needs for the combobox, so I can save them myself
08
use shadcnio to show me three pricing sections with a yearly toggle and how they differ

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 shadcnio in 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 shadcnio until 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_plan returns 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 shadcnio as 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 shadcnio in 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.json never appears.
Claude reads the file at startup only: quit it completely, since closing the window isn't enough, and reopen it. Still missing? mcp.log in ~/Library/Logs/Claude (macOS) or %APPDATA%\Claude\logs (Windows) says why, often a JSON typo or no Node for npx.

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.

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