shadcn MCP

The MCP server that lets an agent work with shadcn registries directly — search for a component, inspect what it pulls in, and run the install, all without me leaving the conversation.

Overview

shadcn components live in registries, and the MCP server exposes those registries as tools. Instead of me copying npx shadcn add commands by hand, the agent can search the registry, read a component's source and dependencies, then install it. It's configured in this repo's .mcp.json.

Setup

This is the actual .mcp.json from this project:

{
  "mcpServers": {
    "shadcn": {
      "command": "npx",
      "args": ["shadcn@latest", "mcp"]
    }
  }
}

Drop that at the project root and the agent picks up the server on next launch.

Tools it exposes

• Search items across configured registries.
• Inspect an item — its source, files and registry dependencies — before installing.
• Generate and run the add command to install components into the project.

When to use it

Whenever I'm pulling components into a shadcn-based project — including Morpha UI itself, which is built on the shadcn base. It pairs with the Component from Figma prompt: find or scaffold the primitive via the MCP, then theme it with Morpha tokens.