Claude

Set ReUI up in Claude once, then build UI from the entire ReUI registry just by chatting. Pick your Claude below - the two setups differ only in how you add the server. The endpoint is always the same URL, https://mcp.reui.io, over Streamable HTTP, the same one every agent uses - see MCP Server for the shared background.

Setup

claude mcp add --transport http reui https://mcp.reui.io

/mcp

claude mcp login reui

claude mcp list

curl -fsSL https://mcp.reui.io/install | node -

https://mcp.reui.io

Build with ReUI

Describe the interface you want in plain language and Claude pulls the right ReUI components, examples, and blocks from the registry, then wires them into your project.

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.

Add a data-grid of orders with sorting, column filters, pagination, and row selection, wired to my /api/orders endpoint.

Build a multi-step "create project" wizard with the ReUI stepper and form components, with validation on each step.

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 27 components and every c-* example) install with no license. To let Claude install premium blocks and icons 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:

REUI_LICENSE_KEY=your-license-key-here

{
  "registries": {
    "@reui": {
      "url": "https://reui.io/r/{style}/{name}.json",
      "headers": {
        "Authorization": "Bearer ${REUI_LICENSE_KEY}"
      }
    }
  }
}

That is it - Claude 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.

Headless and CI

For Claude Code runs without a browser (CI, remote sessions), create a personal token at Account → MCP and pass it as a Bearer header instead of the browser sign-in:

claude mcp add --transport http reui https://mcp.reui.io \
  --header "Authorization: Bearer reui_pat_your_token_here"

In a config you commit, keep the token in the environment and let Claude Code substitute it, exactly as the installer does:

{
  "mcpServers": {
    "reui": {
      "type": "http",
      "url": "https://mcp.reui.io",
      "headers": {
        "Authorization": "Bearer ${REUI_MCP_TOKEN}"
      }
    }
  }
}

Once a header is set, that is the credential Claude Code uses. It will not fall back to the browser flow, so a bad or lapsed token shows up as a failed connection rather than a sign-in prompt.

Tokens expire after 90 days by default (30, 60, 90 and 180 are offered, plus No expiry for pipelines that cannot rotate). Nothing emails you beforehand, so an expired token simply starts returning 401 - create a fresh one at Account → MCP and update the header. Existing tokens keep whatever lifetime they were issued with.

Troubleshooting

Most hiccups are a stale browser sign-in, and reconnecting fixes them. The one exception is a personal token, which cannot be re-authenticated - it has to be replaced.

• Tools missing, greyed out, or "not connected" - the server did not finish connecting. To fix it, run /mcp in Claude Code and re-authenticate reui (or toggle the connector off and on in Claude Desktop), then restart Claude.
• 401 and you sign in through your editor - your ReUI session expired. To fix it, run /mcp in Claude Code and re-authenticate reui (or toggle the connector off and on in Claude Desktop) to sign in again.
• 401 and you use a personal token (headless or CI) - the token has expired or been revoked. Re-authenticating will not help: /mcp renews the browser sign-in, not the Authorization header your job sends, and Claude Code reports a rejected header as a failed connection rather than falling back to OAuth. Create a new token at Account → MCP and update the header or CI secret. The 401 body names which of the two it was.
• Requests hang or the session drops mid-build - long sessions can lose the connection. To fix it, run /mcp in Claude Code and re-authenticate reui (or toggle the connector off and on in Claude Desktop) and retry your last prompt.
• Sign-in appears to work but every call still 401s - check whether you have an Authorization header on the reui entry in .mcp.json. A configured credential is sent on every request and overrides the OAuth credential the sign-in stores, so while it is there running /mcp and re-authenticating reui cannot take effect. The two are alternatives, not layers: use the header only on the headless path, and remove it if you want the browser sign-in.
• "Your free ReUI MCP allowance ... is used up" in a tool result - the free plan has a daily MCP request allowance and today's is used up. It arrives as a normal tool result Claude shows you, not an HTTP error, so there is no status code to look for, and it resets at UTC midnight. For unlimited requests use a Pro or Ultimate license key, or a personal token from a licensed account, as your MCP credential, or wait for the reset.
• 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.