Shadcn MCP for Amp

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

Install

Run this in your terminal:

Run it once signed in with an active Pro subscription — the URL carries your personal token, so treat the command line 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 →

amp mcp add writes to your Amp config, so the server is ready for the next prompt — no restart. Since shadcn.io carries the token in the URL, you don't need --header "Authorization: …" the way some other MCP servers require for auth.

Using headers instead

If your team policy forbids tokens in URLs, Amp supports a --header flag:

amp mcp add shadcnio --header "Authorization=Bearer YOUR_TOKEN" https://www.shadcn.io/api/mcp

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 Amp 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 in your shell. Files land under components/ui/.

Name the server explicitly ("use shadcnio…") when multiple MCPs are configured, or Amp picks one at random or skips tools entirely.

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

Manage the connection

Three CLI commands cover the lifecycle:

amp mcp list
amp mcp remove shadcnio
amp mcp --help

amp mcp list prints every configured server with live status. Remove and re-add to rotate a token. To disable without removing, edit Amp's config file directly and flip the enabled field if your Amp version supports it — otherwise amp mcp remove + re-add is the cleanest path.

If your Pro subscription lapses, the next tool call returns 403. Resubscribing restores access on the following request — no reconfigure, no reinstall. The token itself stays valid across subscription gaps.

FAQ