MCP

Ask your agent to find and install Efferd blocks. Pick a client, then connect the shadcn MCP server.

Quick start

Pick the client you use. Each page shows where the server config goes and how to confirm it is connected.

Claude

Codex

Cursor

Grok

OpenCode

VS Code

Kilo Code

Zed

Antigravity

Windsurf

Gemini CLI

Command Code

If your client is not listed, add a local server named shadcn that runs npx shadcn@latest mcp. Most clients use this shape. The file name depends on the client.

mcp.json

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

Claude uses .mcp.json, Cursor uses .cursor/mcp.json, and VS Code uses .vscode/mcp.json with a servers key. For any other client, look up the file name in your client's MCP docs.

What is MCP?

Model Context Protocol (MCP) is how an agent talks to tools outside the chat. The shadcn MCP server is that tool for registries.

It reads components.json, then browses and installs blocks from the registries listed there, including @efferd.

The registry has to be in the project first. Quick Setup covers that. Connecting the server does not add it.

How it works

1

The server reads the project

It uses the registries already in components.json, including the style you chose and a Pro token when one is set.

2

You ask for a block

Describe what you need the same way you would ask someone on your team. For example, a hero from @efferd.

3

The agent runs the install

It turns that request into a registry command and runs the shadcn CLI.

4

The block lands in the project

Files are added where your setup expects them. Review the diff before you keep it.

Read more in the shadcn MCP documentation.