Connect 21st.dev to Conductor
Community marketplace of React components, templates, shadcn themes and shaders, with a hosted MCP server for agents. Browsing is free; copying more than a few components a day needs a membership.
MCP serverOfficialChecked 2026-11-16
Before you start
- Conductor installed (see its MCP documentation (opens in a new tab)).
- 21st.dev is available on macOS, Windows, Linux and the web.
- Get an API key at 21st.dev/mcp and set it as
API_KEY_21STin your environment. Keys from the old Magic console no longer work. AI generation tools only appear when your account has AI access. Each component page also shows its own shadcn CLI command.
Step 1: Add 21st.dev 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 --transport http 21st-dev https://21st.dev/api/mcp --header 'x-api-key: ${API_KEY_21ST}'Or share it with your team
Add this to
.mcp.jsonat the project root and commit it. Claude Code sessions in every workspace on that branch pick it up..mcp.json { "mcpServers": { "21st-dev": { "type": "http", "url": "https://21st.dev/api/mcp", "headers": { "x-api-key": "${API_KEY_21ST}" } } } }Or edit Codex's config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.21st-dev] url = "https://21st.dev/api/mcp" env_http_headers = { "x-api-key" = "API_KEY_21ST" }Good to know- Start a new session in Conductor after adding a server, so the agent loads it.
- Set
API_KEY_21STin your environment before you start Claude Code. It reads the value each time it connects, so the token stays out of the config. - Codex reads
API_KEY_21STfrom your environment each time it connects, so the token stays out of the file.
Step 2: Check it's connected
Terminal claude mcp listIn a Conductor session, click the plug icon in the composer or run
/mcp-statusto see each server's status.Step 3: Try a first request
Ask Conductor something that only works with 21st.dev connected:
Say to Conductor Search 21st.dev for a pricing section that fits this page and show me how to adapt it.
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 addonly apply to the folder you ran it in, so use--scope useror a committed.mcp.json. - Conductor runs on macOS. Environment variables for local servers can go in
.conductor/settings.local.toml, under[environment_variables].






