Everything your agent needs
to build with shadcn/ui

16 live tools over the Pro registry: every block in 25 categories, 24 themes, the Figma kit and icon search. The agent finds the block that does what you asked, reads its install command, usage and source, plans a whole page as a stack of blocks, applies a theme and finds icons, all from the live catalog. Install commands run as-is: no invented ids, no broken imports.

Pasted code goes stale and burns context. The MCP is live and the agent asks for exactly what it needs: a ranked search is about a thousand tokens, one block with its install command a few hundred, against tens of thousands for pasted source. You stop re-teaching your agent what exists every conversation.

The official shadcn MCP (npx shadcn@latest mcp) browses registries listed in components.json and installs items. The Pro server adds what a registry listing cannot express: ranked search over what blocks do, page planning, usage snippets, complete themes, Figma kit links, icon search and account tools, with no local setup. Use both: the official server for base components, this one for Pro blocks and pages.

The server takes both: Authorization: Bearer <key> on the plain endpoint, or ?token=<key> in the URL. Use the header wherever your client can set one; ChatGPT, Claude Desktop connectors and Warp cannot, so they use the URL. A URL can end up in logs, so treat it like a password.

Name the server once: "use shadcnpro to add a date picker block". After that the agent picks the tools itself; the server also sends it short instructions on when to use what. Some clients cap how many tools they load across servers, so switch off servers you are not using in a project.

Ask the agent to call whoami: it answers with your email, plan and the requests left this minute. From a terminal, the curl command on the setup page does the same without any client in between.

search_blocks ranks blocks by what they do and understands synonyms, so "modal" finds the dialogs and "login" the sign-in screens. get_block then returns the install command, the import line and the files in one call. The agent runs the shadcn CLI command in your project after you approve, and the block arrives with the shadcn/ui components it uses.

plan_page turns a brief into an ordered stack of blocks for a landing, pricing, contact, blog, sign-in, sign-up, dashboard, onboarding or 404 page, or for a custom list of sections. It returns a pick with alternatives per section, one install command for the stack and an app/page.tsx skeleton. The build-page prompt walks the agent through it.

get_theme returns any of the Pro themes as a complete :root and .dark variable set or a shadcn preset code. get_figma_link points at a component in the Pro Figma kit for handoff or for the Figma MCP. search_icons and get_icon search the icon sets shadcn/ui projects use and return the real import for the set your project already has.

Yes. The MCP server is included with every Pro plan, monthly or yearly. Your key is tied to your account; without an active subscription the server answers 403 with a link to the plans.

The server answers 403 once your subscription ends. The key itself stays valid, so when Pro is active again the same config works within a minute, with nothing to reinstall. Blocks already in your projects stay yours under the license.

No. Data flows one way, from the Pro registry to your agent; your project files never leave your machine. The server sees only the tool calls themselves, such as a search query or a block id, which it logs to improve the catalog.

300 requests a minute per key, shared with the CLI registry. A prompt takes a handful of calls, so only an agent stuck in a loop reaches it; past the limit the server answers 429 with a Retry-After header, and whoami shows how many requests are left.

Yes. On Agency (up to 5 seats) and Enterprise (unlimited seats), every member of the workspace has Pro and creates their own key from their own account. Nobody shares a key, and removing a member ends their access at once.

Commit the variant that reads the key from an environment variable (SHADCNPRO_LICENSE_KEY) and let each developer set it locally. Every client page shows its team variant: ${env:...} in Cursor, ${...} in Claude Code’s .mcp.json, a prompted input in VS Code, bearer_token_env_var in Codex.

401: the key is missing or invalid; copy the config again from your account page. 403: the key is valid but the account has no active Pro; fix billing and the same key works again. 429: more than the per-minute limit on one key; stop the loop and wait the Retry-After seconds.