Anthropic
One terminal command. Once connected, Claude Code searches every Pro block, reads the real install command and plans whole pages from the live registry, with 16 tools and 4 prompts. Included in every Pro plan.
Snippets below use a placeholder. Your account page fills them with your key.
Add the server
Run once; --scope user makes it available in every project.
claude mcp add --transport http --scope user shadcnpro https://pro.shadcn.co/api/mcp \
--header "Authorization: Bearer YOUR_LICENSE_KEY"Check it
Inside Claude Code, /mcp lists the server and its 12 tools.
/mcpCheck the connection
Ask the agent to call whoami on the shadcnpro server. It answers with your email and plan when the key works.
Use shadcnpro to call whoami.Then
Name the server once so Claude Code picks the right tools; after that it finds, inspects and installs blocks on its own.
Subscribe to any Pro plan, open Account › MCP server, create a key and copy the config for your client with the key already filled in. The endpoint is https://pro.shadcn.co/api/mcp and the key travels as an Authorization: Bearer header. It takes about a minute per client.
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.
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.
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.
Copy the whole config again, restart the client (most read their config once at start) and check the transport: the server speaks MCP over HTTP, so a local-only client needs the mcp-remote bridge. Behind a proxy, pro.shadcn.co needs HTTPS access. The troubleshooting guide has the full list.
16 tools, every Pro block, 24 themes and the Figma kit, in 20 AI clients. Included in every Pro plan, monthly or yearly.
Secure payment. 7-day free trial. Cancel anytime.
