Planes

Components

Docs / MCP

MCP

Let AI agents browse and install Planes components through the shadcn MCP server.

Overview

The shadcn CLI ships a Model Context Protocol server that exposes every registry configured in your components.json to agents like Claude Code, Cursor, and VS Code. With Planes registered, you can ask your agent to find, install, and wire up components in plain language — it resolves the registry, runs the install, and edits your code in one pass.

01

Configure the registry

Same one-time setup as installation, so skip this step if your project is already configured. The Authorization header is only exercised for Pro components — set PLANES_LICENSE_KEY in your environment if you have a Pro license.

One command merges the @useplanes registry into your components.json, writes your key to .env.local, and keeps it out of git.

Run init — it configures everything for you.

pnpm dlx @useplanes/cli init --key your_key
02

Add the MCP server

The CLI can configure your client for you — pass claude, cursor, vscode, or codex:

pnpm dlx shadcn@latest mcp init --client claude
Add to Cursor

In Cursor, skip the terminal — this registers the server in one click.

Or register it manually. For Claude Code, that is a .mcp.json at your project root:

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

Try it

Restart your agent, then prompt it naturally:

  • “Show me the components available in the @useplanes registry”

  • “Install the command palette from @useplanes”

  • “Add the pricing table from @useplanes to my landing page”