Shadcn MCP for Zencoder

One MCP URL gives Zencoder live tools to search, preview, and install every block, component, and icon on shadcn.io — no hallucinated props, no broken installs.

Install

In Zencoder, open the menu (the ... in the top-right), select Agent tools, click Add custom MCP, name it shadcnio, and paste this configuration:

Click Install once signed in with an active Pro subscription — the config carries your personal token through the mcp-remote bridge, so treat the URL like an API key. Pro starts at $19/mo and includes MCP access across every editor plus 6,000+ production-ready blocks. Not Pro yet? See what you unlock →

Zencoder's Add custom MCP form takes a flat config (no outer mcpServers wrapper) — the UI adds the name and wrapping itself. Pasting a nested Cursor-style config won't parse.

Share with your team

Zencoder stores MCP configs per-install, so there's no committed-repo pattern. For teams, share the setup steps and let each teammate enter their own token from /dashboard/account. A Team or Organization plan gives every workspace member their own Pro entitlement.

Install your first block

use shadcnio to install hero-announcement into my project

What Zencoder actually does, in order:

1. search_items({ query: "hero-announcement" }) to confirm the slug resolves.
2. get_item({ name: "hero-announcement" }) for a cheap metadata peek.
3. get_install_command({ name: "hero-announcement" }) — returns a shadcn add https://www.shadcn.io/r/hero-announcement.json?token=… URL with your token already in the query string.
4. Runs it through Zencoder's shell tool. Files land under components/ui/.

Name the server explicitly ("use shadcnio…") when multiple MCPs are configured.

The example above uses hero-announcement, a Pro block — the install runs once you're signed in with an active subscription.

Manage the connection

Return to Agent tools to edit, disable, or remove shadcnio. Zencoder reloads tools on save, so changes take effect without restarting.

If your Pro subscription lapses, mcp-remote surfaces the 403 response in Zencoder's tool log. Resubscribing restores access immediately — the token stays valid across subscription gaps.

FAQ