Your AI editor just learned shadcn/ui.

22 live MCP tools for every shadcn.io component and block (6,231 sections and app screens): for React on Base UI, Ark UI, Radix or React Aria, and for Vue, Svelte and Solid on Ark UI, plus 294k icons across 222 libraries. Your agent sets up the project, finds the component (or the demo of the pattern it needs, or the block for a whole section), plans a page as a stack of blocks, gets its install, usage and a working demo in one call, and reads the exact props of any part. Install commands run as-is: no hallucinated props, no broken imports.

Docs go stale and burn context. MCP is live, and your agent asks for just what it needs: the catalog by category is a few hundred tokens, one part's props are a few hundred, against tens of thousands to paste the docs. You stop paying to re-teach your agent shadcn every conversation.

Claude Code, Cursor, VS Code, Windsurf, Zed, JetBrains, Codex and 31 more each have a setup guide in the docs, and any client that speaks MCP over HTTP works. Setup takes about a minute per editor.

Yes. The MCP serves the same registry the site shows, for React, Vue, Svelte and Solid. Your agent passes the framework (and for React, the base) to each tool, reading both from your package.json, so a Vue project gets Vue components and a Radix project gets Radix ones.

Copy your personal MCP URL from /dashboard/mcp and paste it into your editor's MCP config. For Claude Code, it is one command: claude mcp add --transport http --scope user shadcnio https://www.shadcn.io/api/mcp --header "Authorization: Bearer YOUR_TOKEN". The setup guide for each client shows its own config.

The server takes the token either way: as ?token=… in the URL, or as an Authorization: Bearer header on the plain endpoint. Use the header where your client lets you set headers, because a token in a URL's query can end up in logs along the way.

Name the server in your prompt: use shadcnio to add a date picker. Some clients also let you switch each server's tools on or off, and some cap how many tools they load across all servers, so turn off the ones you aren't using.

Call whoami: it returns your email, your plan and how many calls you have left this minute. An answer means the URL works. If your client only runs local servers, bridge it with npx -y mcp-remote followed by your URL, which needs Node.js.

22 tools in seven groups: discover (list_components, search_components, search_demos), inspect (get_component, get_component_api and others), blocks, install, icons, design and account. Each has its own page under /mcp/tools with a sample call and what it returns.

search_components ranks by what a component does, so a modal finds the dialog. get_component then returns its install, usage and a demo in one call, with include choosing which. get_component_api reads one part's props, and get_demo fetches another demo of the same component.

The block tools cover all 6,231 blocks: search_blocks finds one by what it does, list_blocks is the catalog by category, get_block returns it with its install, FAQ, preview links or source, and plan_page turns a brief (a landing page, an app shell) into a stack of blocks. Blocks are part of Pro like the rest of the MCP.

search_icons finds an icon by name or meaning across 294k icons in 222 libraries, and get_icon returns it: the import from the set's package when it has one, otherwise a component (for React, one CLI command). list_icon_libraries shows which sets exist.

search_designs and get_design return a brand's design system as a DESIGN.md (colors, type, spacing, components), and search_templates finds a starting template. get_guide covers forms, theming, colors and RTL, and get_project_setup sets a new project up once.

Yes. MCP is included with every Pro plan (monthly, yearly, or lifetime). Your MCP URL carries a personal token tied to your account. Without an active Pro, the server returns 403 with a link to the plans.

The server answers 403 once your Pro ends, with an upgrade link. Your token stays valid, so when Pro is active again the same URL works, within a few minutes and with no reinstall. What you already put in your projects stays yours, as the license says.

No. MCP is one-way: shadcn.io registry data flows to your agent, and your project files never leave your machine. The server only sees the tool calls themselves, like a component's name or a search.

Treat it like an API key: anyone with it can use your Pro access. Keep it out of git, screenshots and public logs. If it leaks, regenerate your token on your account page: the old URL stops working within a few minutes, and you put the new one in each client.

600 calls a minute per token: plenty for sustained agent use, since a prompt takes a handful of calls. Past it, the server returns 429 with a Retry-After header. whoami shows how many calls you have left this minute.

Yes, on the Team and Organization plans: a member of a workspace whose owner has Pro has Pro too, and gets their own personal MCP URL on their own dashboard. Nobody shares a token. Individual licenses cannot be shared.

Team covers up to 5 seats within one company, and Organization covers unlimited seats within the purchasing organization. Workspace owners and admins invite members, and each member needs to belong to the same company or legal entity.

Commit the version of the client's config that reads the token from an environment variable (SHADCNIO_TOKEN), and let each person set their own. The setup guide of each client that supports a project file shows it, such as .mcp.json for Claude Code.

Call whoami with curl, outside your editor. An email in the answer means your URL works and the client's config is the problem. An error tells you which of the cases below applies.

The token is missing or not valid. Copy your whole URL again from /dashboard/mcp, ?token= included, and replace it in every config. After you regenerate a token, the old URL stops working everywhere.

The token is valid but the account has no Pro, so the MCP is refused with an upgrade link. Pro covers it on any plan, and the same URL works again within a few minutes of Pro starting.

You passed 600 calls a minute on your token, usually an agent stuck in a loop. Wait the number of seconds in the Retry-After header. The same 429 also comes from too many refused calls (no token or a wrong one) from one network: fix the token, then wait a minute.

Copy the whole URL, restart the client or reload its servers (most read the config once at startup), and check the transport: the server speaks MCP over HTTP, so a local-only client needs npx -y mcp-remote. Behind a proxy, the client needs HTTPS access to the site.