Lovable

Lovable connects to ReUI through a single chat connector, so you can build UI from the ReUI registry right inside your chat. The endpoint is https://mcp.reui.io, the same one every agent uses - see MCP Server for the shared background.

Custom MCP servers are available on every Lovable plan. A chat connector only gives Lovable context while it builds for you: it is never part of your published app, and your app's visitors can never reach it.

Connect ReUI

Server name:    reui
Server URL:     https://mcp.reui.io
Authentication: OAuth (default)

The ReUI skill

You do not install anything - the skill rides on the MCP from mcp.reui.io, no separate registry to add. Once the connector is authorized, the Lovable Agent gets ReUI's tools, and it can call get_agent_skill to load the full ReUI workflow (the reuse-first rule and the discover, install, adapt order) as a document. If a build ever drifts off-pattern, tell it to "follow the ReUI skill" to reload that workflow.

Build with ReUI

Describe the interface you want in plain language and Lovable 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 20 components and every c-* example) install with no license. Since Lovable builds on the shadcn/ui model (Vite + React), connect GitHub first and apply the steps below in the synced repo, where the Agent runs the CLI. To let Lovable 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 - Lovable 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

Lovable is a browser product and has no headless or CI mode of its own, so the OAuth sign-in above is the path to prefer. If you would rather hand it a credential than a session, the same form offers Bearer token or API key as an alternative to OAuth (default). Pick it, create a personal token at Account → MCP, paste the token value on its own - just reui_pat_..., with no Authorization: prefix and no ${...} environment placeholder, since the field is sent exactly as written - then click Add server.

Tokens expire after 90 days by default (30, 60, 90 and 180 are offered, plus No expiry). 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 connector. 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.

• No Custom MCP card in Connectors - on Business and Enterprise workspaces an admin can turn custom MCP servers off as a category. Ask them to re-enable Custom MCP in the connector admin settings.
• Tools missing, greyed out, or "not connected" - the server did not finish connecting. To fix it, open Connectors, remove and re-add the reui server, and authorize again, then restart Lovable.
• 401 and you signed in with OAuth - your ReUI session expired. To fix it, open Connectors, remove and re-add the reui server, and authorize again to sign in again.
• 401 and you used a bearer token - the token expired or was revoked. Re-adding the connector will not help, since it sends the token you pasted rather than a browser session. Create a new token at Account → MCP and paste it in again. 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, open Connectors, remove and re-add the reui server, and authorize again and retry your last prompt.
• Sign-in appears to work but every call still 401s - check whether you picked Bearer token or API key instead of OAuth (default) on the connector form. 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 removing and re-adding the server with OAuth (default) 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.