Bolt

Connect the ReUI MCP server to Bolt and build UI from the ReUI registry by chat.

Bolt connects to the ReUI registry as a custom connector: add the ReUI MCP server once in your account, turn it on in a project, and you can build UI straight from chat. For the shared background (the tools, the plan limits, the sign-in flow) see the MCP server overview.

Connect ReUI

Add the ReUI connector

Open the Connectors (MCP) page: click the plus icon in the chatbox, choose Connectors, then Manage connectors (the same page is under Settings → Connectors). Click Custom MCP server and fill in the form:

Connector settings

Name: ReUI
URL: https://mcp.reui.io
Transport type: HTTP
Authentication: MCP OAuth

Then click Connect. A "Connected" status in the upper right confirms the server is set up.

Sign in with ReUI

Choosing MCP OAuth means Bolt runs a sign-in flow rather than asking for a key. Approve the "Sign in with ReUI" prompt in the browser and Bolt is ready to use. If you do not have a ReUI account yet, a free one is created for you during this flow, so there is nothing to set up in advance.

Turn it on in your project

Connectors are added at the account level and enabled per project. Open the project, click the plus icon in the chatbox, choose Connectors, and toggle ReUI on. If you want it on everywhere, select Auto-enable for all projects when you add the connector.

Personal tokens are for headless clients

ReUI also issues personal tokens (reui_pat_...) at Account → MCP for CI and other runs with no browser. Bolt has a browser, so MCP OAuth is the path here. Its form does offer an API key option, but Bolt does not document which header it sends that key in, so we cannot promise a ReUI token works through it - use the sign-in flow instead.

The ReUI skill

There is nothing to install. Bolt is a hosted builder, so it cannot run a local installer, and it does not need to: the ReUI tools carry their own usage guidance, and Bolt can call get_agent_skill to load the full build workflow (browse the registry, pull real component source, assemble screens) as a document. If a build drifts off-pattern, tell it to "follow the ReUI skill".

Build with ReUI

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

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 Bolt 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:

Apply both steps inside the Bolt project itself, so the files live in the workspace Bolt wires your UI into.

Add your license key

Copy your key from Account → Licenses into .env.local at the project root:

.env.local

REUI_LICENSE_KEY=your-license-key-here

Add the @reui registry to components.json

components.json

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

The shadcn CLI expands ${REUI_LICENSE_KEY} from .env.local, so leave it as a variable here. It belongs in components.json only - never paste that placeholder into a connector form, which has no environment to expand it from.

That is it - Bolt 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

Almost every hiccup is a connector that is off in this project, or a stale sign-in.

Tools missing or "not connected" - most often the connector is off for this project. To fix it, click the plus icon in the chatbox, choose Connectors, and check that ReUI is toggled on. If it is, open Manage connectors and reconnect ReUI.
Some ReUI tools are missing but others work - tools can be deselected per connector. To fix it, open Manage connectors, select ReUI, click the three-dot menu, choose Edit, and re-select the tools you need. That setting applies to every project.
401 or "authentication required" - your ReUI session expired. To fix it, open Manage connectors, reconnect ReUI, and authorize again.
Requests hang or the session drops mid-build - long sessions can lose the connection. To fix it, reconnect ReUI from Manage connectors and retry your last prompt.
Sign-in appears to work but every call still 401s - check whether you picked API key instead of MCP OAuth when adding the server. A pasted credential is sent on every request and takes precedence over an OAuth session, so if it is wrong or expired the calls keep failing. Fix it by re-adding the server with MCP OAuth selected, or by replacing the credential with a valid one. The two are alternatives, not layers.
429 "daily limit reached" - you hit the free limit of 100 tool calls per day. 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.

Replit OpenCode

On This Page

Connect ReUI The ReUI skill Build with ReUI Unlock premium items Troubleshooting

Connect ReUI

Add the ReUI connector

Connector settings

Name: ReUI
URL: https://mcp.reui.io
Transport type: HTTP
Authentication: MCP OAuth

Then click Connect. A "Connected" status in the upper right confirms the server is set up.

Sign in with ReUI

Turn it on in your project

Personal tokens are for headless clients

The ReUI skill

Build with ReUI

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

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

Apply both steps inside the Bolt project itself, so the files live in the workspace Bolt wires your UI into.

Add your license key

Copy your key from Account → Licenses into .env.local at the project root:

.env.local

REUI_LICENSE_KEY=your-license-key-here

Add the @reui registry to components.json

components.json

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

That is it - Bolt 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

Almost every hiccup is a connector that is off in this project, or a stale sign-in.

Tools missing or "not connected" - most often the connector is off for this project. To fix it, click the plus icon in the chatbox, choose Connectors, and check that ReUI is toggled on. If it is, open Manage connectors and reconnect ReUI.

Some ReUI tools are missing but others work - tools can be deselected per connector. To fix it, open Manage connectors, select ReUI, click the three-dot menu, choose Edit, and re-select the tools you need. That setting applies to every project.

401 or "authentication required" - your ReUI session expired. To fix it, open Manage connectors, reconnect ReUI, and authorize again.

Requests hang or the session drops mid-build - long sessions can lose the connection. To fix it, reconnect ReUI from Manage connectors and retry your last prompt.

Sign-in appears to work but every call still 401s - check whether you picked API key instead of MCP OAuth when adding the server. A pasted credential is sent on every request and takes precedence over an OAuth session, so if it is wrong or expired the calls keep failing. Fix it by re-adding the server with MCP OAuth selected, or by replacing the credential with a valid one. The two are alternatives, not layers.

429 "daily limit reached" - you hit the free limit of 100 tool calls per day. 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.