Connect the ReUI MCP server to Conductor so every parallel workspace can build UI from the ReUI registry.
Conductor runs Claude Code, Codex, Cursor, and OpenCode in parallel on your Mac, each task in its own workspace, branch, and checkout. It connects to ReUI a little differently from every other guide here, and the difference is worth understanding before you start: Conductor does not define its own MCP config format. It uses the MCP configuration the underlying agent already loads for that session. So you do not configure ReUI in Conductor, you configure it for Claude Code (or Codex, or Cursor) and Conductor picks it up.
That turns out to be an advantage. Conductor creates each workspace as a , one workspace per branch, so a config file committed at your repository root is present in every workspace Conductor creates - existing ones and ones you have not made yet. Set ReUI up once and every parallel agent has it.
For the shared background (the tools, the plan limits, the sign-in flow) see the .
Connect ReUI
Add ReUI to your repository
Claude Code sessions read .mcp.json from the project root, and Conductor states that a repository with one there gives its Claude Code sessions those servers. Create it at the root of the repo you open in Conductor:
Commit it. Because every workspace is a checkout of the repo, committing is what makes ReUI show up in workspaces created later, rather than only in the one you are in now.
Running Codex sessions instead? Codex reads ~/.codex/config.toml or .codex/config.toml, and Cursor Composer reads the project-level .cursor/mcp.json from that workspace checkout. The Codex and Cursor guides cover both, and the entry is equivalent.
Sign in with ReUI
The sign-in is the underlying agent's, not Conductor's. For Claude Code, the first ReUI tool call opens a "Sign in with ReUI" prompt in your browser; approve it and you are connected. A free ReUI account is created in that flow if you do not have one. See the Claude guide for the full flow and its /mcp commands.
If you are fanning out across many workspaces at once, the token setup below is the more predictable option, since it authenticates from the config itself rather than through a browser prompt per session.
Confirm the connection
Conductor shows MCP server status in the chat composer, and there is an MCP status dialog with a Refresh status option. Open it after adding or editing the config: reui should be listed there. If you edited the file while a session was running, use Refresh status rather than assuming it reloaded.
Headless and CI
To authenticate from the config rather than a browser, create a personal token at Account → MCP (it looks like reui_pat_...) and add it as a header. Claude Code substitutes ${VAR} in a server's url and headers, so keep the token in your environment and commit the file safely:
Then export REUI_MCP_TOKEN in the environment Conductor launches agents from. This is the one form that stays safe in a committed file, which matters here more than elsewhere: .mcp.json is the file every workspace inherits, so a pasted token would be committed and shared across all of them. When the variable is unset, Claude Code sends the literal ${REUI_MCP_TOKEN} text and ReUI rejects it with a 401.
Tokens expire after 90 days by default (30, 60, 90 and 180 are offered, plus No expiry for pipelines that cannot rotate). Nothing warns you beforehand, so an expired token simply starts returning 401 across every workspace at once, and has to be replaced rather than re-authenticated.
The ReUI skill
Run the one-line installer from the repository root so the agents Conductor launches follow ReUI's build workflow:
Terminal
curl -fsSL https://mcp.reui.io/install | node -
It writes the skill into the project (.claude/skills/reui and .agents/skills/reui), which is exactly the right place here for the same reason .mcp.json is: commit it and every workspace checkout carries it. Note that the installer also adds a reui entry to ~/.codex/config.toml on your machine.
The same workflow is available at runtime through the server's get_agent_skill tool, so nothing breaks if you skip the install.
Build with ReUI
Describe the interface you want in plain language and the agent pulls the right ReUI components, examples, and blocks from the registry, then wires them into that workspace. Because each workspace is its own branch, this is a natural fit for trying two designs side by side.
Prompt
Use ReUI to scaffold an admin app - the app-shell with a collapsible sidebar and top bar, and a dashboard page with stat cards and a chart.
Prompt
Add a data-grid of orders with sorting, column filters, pagination, and row selection, wired to my /api/orders endpoint.
Prompt
Build a multi-step "create project" wizard with the ReUI stepper and form components, with validation on each step.
Prompt
Add a kanban board for support tickets with drag and drop, grouped by status, and a filters bar above it.
Unlock premium items
Free items (the 20 components and every c-* example) install with no license. To let your agents install premium blocks, icons, and templates too, grab a Pro or Ultimate license - one license unlocks the whole premium registry and removes the daily MCP request limit. Then add your key to the project - two quick steps:
.env.local is normally gitignored, so unlike .mcp.json it does not travel into new worktrees by itself. Export the variable in your shell profile if you want every workspace to pick it up.
The shadcn CLI expands ${REUI_LICENSE_KEY} here. Claude Code expands ${VAR} in .mcp.json too, but the two files want different values: the registry wants your license key, the MCP header wants a personal token, so keep them in separate variables.
That is it - your agents can now install any premium item the MCP returns, and free items keep working through the same config. See License Setup for the full guide, or compare plans on the Pricing page.
Troubleshooting
Because the config belongs to the underlying agent, most fixes live in that agent's guide. The Conductor-specific part is that a change made in one workspace is not a change everywhere.
Tools missing in a new workspace but fine in an older one - the config was added without being committed, so the new worktree checked out a branch that does not contain it. Commit .mcp.json (and the skill directory) and create the workspace again.
Tools missing, greyed out, or "not connected" - open the MCP status dialog and use Refresh status. If reui is still absent, confirm .mcp.json sits at the repository root of that workspace's checkout, not just in your original clone.
401 and you signed in through the browser - your ReUI session expired. Re-authenticate in the underlying agent, as the Claude guide describes.
401 and you use a personal token - the token has expired or been revoked, or REUI_MCP_TOKEN is unset in the environment Conductor launched the agent from, in which case the literal placeholder was sent. Re-authenticating will not help. Create a new token at Account → MCP. The 401 body names which of the two it was.
429 "daily limit reached" - you hit the free limit of 100 tool calls per day. Parallel workspaces share one ReUI account, so several agents running at once draw down the same daily allowance. Sign in with your ReUI license for unlimited access, or wait for the next day.
Every ReUI call fails and nothing asks you to sign in - the stored OAuth connection is dead (revoked, expired, or invalidated after a suspicious reuse), and the client is silently retrying a credential that can never work again. Account → MCP shows the connection as Disconnected when this is the case. Reconnect the same way as the 401 fix above; retrying without signing in again cannot recover it.