Replit

Replit connects to ReUI in one step: add the ReUI MCP server to your Replit Agent, and you can build UI from the ReUI registry by chat. The endpoint is https://mcp.reui.io, the same one every agent uses - see MCP Server for the shared background.

Connect ReUI

Display name:    reui
MCP Server URL:  https://mcp.reui.io

The ReUI skill

You do not install a separate skill - it rides on the MCP from mcp.reui.io, no separate registry to add. Once connected, the Replit Agent gets ReUI's tools and can call get_agent_skill to load the full workflow (discover, read the API, install, then adapt by reuse) as a document. If a build ever drifts off-pattern, tell it to "follow the ReUI skill" to reload it.

Build with ReUI

Describe the interface you want in plain language and Replit 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

Replit runs a full Linux workspace, so the Agent installs items with the shadcn CLI directly in the Replit shell, exactly as the MCP returns them. Free items (the 20 components and every c-* example) install with no license. To let Replit 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:

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 - Replit 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.

Using a token instead

For an unattended setup where nobody is there to approve a browser prompt, authenticate with a personal token instead. Create one at Account → MCP (it looks like reui_pat_...), then open Advanced settings in the add-server dialog and define a custom header:

Header name:  Authorization
Header value: Bearer reui_pat_your_token_here

Replit sends the headers you define with every MCP request, so ReUI sees the token on each call. Paste the token itself, not an environment variable reference: the value is sent exactly as written, so a ${...} placeholder arrives at the server as literal text and the request fails with a 401.

Tokens expire after 90 days by default (30, 60, 90 and 180 are offered, plus No expiry for setups that cannot rotate). Nothing warns you beforehand: an expired token simply starts returning 401, and the only fix is to create a new one at Account → MCP and update the header value. Existing tokens keep whatever lifetime they were issued with.

Troubleshooting

Almost every hiccup is a stale sign-in - the fix is to reconnect and authorize again. The one exception is a personal token, which cannot be re-authorized and has to be replaced.

• Tools missing, greyed out, or "not connected" - the server did not finish connecting. To fix it, re-open the MCP settings, run Test & save on reui, and authorize again, then restart Replit.
• 401 and you signed in with ReUI - your ReUI session expired. To fix it, re-open the MCP settings, run Test & save on reui, and authorize again to sign in again.
• 401 and you set an Authorization header - the token expired or was revoked. Running Test & save will not help, since the connection sends the header you typed rather than a browser session. Create a new token at Account → MCP and update the header value. 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, re-open the MCP settings, run Test & save on reui, and authorize again and retry your last prompt.
• Sign-in appears to work but every call still 401s - check whether you filled in the Authorization header field instead of authorizing with ReUI. 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 clearing that header field and running Test & save to authorize, 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.