Skip to content

Connect shadcn/ui to Conductor

Copy-in React components built on Radix and Tailwind. Its MCP server browses, searches and installs items from the default and any namespaced community registry.

MCP serverOfficialChecked 2026-11-16

Before you start

  1. Step 1: Add shadcn/ui to Conductor

    For Claude Code sessions

    Saves the server to your Claude Code user settings, so every Conductor workspace gets it.

    Terminal
    claude mcp add --scope user shadcn -- npx -y shadcn@latest mcp

    For Codex sessions

    Saves the server to ~/.codex/config.toml, which Codex sessions in every workspace read.

    Terminal
    codex mcp add shadcn -- npx -y shadcn@latest mcp

    Or share it with your team

    Add this to .mcp.json at the project root and commit it. Claude Code sessions in every workspace on that branch pick it up.

    .mcp.json
    {
      "mcpServers": {
        "shadcn": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "shadcn@latest",
            "mcp"
          ]
        }
      }
    }

    Or edit Codex's config file

    Add this to ~/.codex/config.toml.

    ~/.codex/config.toml
    [mcp_servers.shadcn]
    command = "npx"
    args = ["-y", "shadcn@latest", "mcp"]
    Good to know
    • Start a new session in Conductor after adding a server, so the agent loads it.
  2. Step 2: Check it's connected

    Terminal
    claude mcp list

    In a Conductor session, click the plug icon in the composer or run /mcp-status to see each server's status.

  3. Step 3: Try a first request

    Ask Conductor something that only works with shadcn/ui connected:

    Say to Conductor
    Search the shadcn registry for a date picker and give me the command to add it to this project.

If it doesn't work

  • Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
  • Each workspace is a separate git worktree. Servers added with plain claude mcp add only apply to the folder you ran it in, so use --scope user or a committed .mcp.json.
  • Conductor runs on macOS. Environment variables for local servers can go in .conductor/settings.local.toml, under [environment_variables].