Shadcn MCP via Smithery

Smithery is an MCP server aggregator and CLI installer. Rather than hand-editing each client's config, Smithery picks the right config file for the editor you name and writes a ready-to-run entry into it.

Install

Run this in your terminal, substituting your client name and Smithery key:

npx -y @smithery/cli@latest install @shadcn-io/mcp --client <CLIENT_NAME> --key <YOUR_SMITHERY_KEY>

Replace <CLIENT_NAME> with one of Smithery's supported clients (e.g. claude, cursor, windsurf, vscode) and <YOUR_SMITHERY_KEY> with the key from your Smithery dashboard. Smithery writes the correct config shape — mcpServers.shadcnio for Cursor, servers.shadcnio for VS Code, etc. — so you don't have to remember each client's quirks.

Pro starts at $19/mo on shadcn.io and includes MCP access across every editor plus 6,000+ production-ready blocks. Not Pro yet? See what you unlock →

When Smithery fits (and when the per-client guide is better)

Smithery is a great fit when:

• You configure MCP across several editors on the same machine and want one installer instead of N JSON files.
• You're doing a clean-machine setup (new laptop, new VM) and want the shortest path to a working config.
• You want Smithery's dashboard to track which servers you've installed across clients.

The per-client setup guide is a better fit when:

• You need editor-specific details (${input:…} variables in VS Code, alwaysAllow in Roo Code, mcp-remote bridges for STDIO-only clients like Zed / LM Studio).
• You're sharing a team config with a custom header form (Authorization: Bearer ${SHADCNIO_TOKEN}) that Smithery's default install doesn't generate.
• You don't want the extra Smithery account on the dependency chain.

For everything Smithery supports, the supported-clients list is the canonical source — it tracks whether a given editor is current or deprecated.

Install your first block

After smithery install finishes, restart (or reload) the target editor and prompt it:

use shadcnio to install hero-announcement into my project

The underlying flow is identical to the per-client guides — search_items → get_item → get_install_command → shadcn add …. Smithery just wrote the config; shadcn.io's tools and the editor's behavior are unchanged.

FAQ