Cursor

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

Cursor connects to ReUI in two quick steps: point it at the hosted MCP server, then sign in and start building UI by chat. The endpoint is https://mcp.reui.io over Streamable HTTP, the same one every agent uses - see MCP Server for the shared background.

Connect ReUI

Add the ReUI MCP server

Add the reui server to Cursor in one click. Cursor opens, shows the server, and asks you to confirm - approve it, then reload.

Add to Cursor

Prefer to set it up by hand? Add ReUI to .cursor/mcp.json in your project, then reload Cursor:

.cursor/mcp.json

{
  "mcpServers": {
    "reui": {
      "url": "https://mcp.reui.io"
    }
  }
}

A remote server needs no type field - Cursor infers Streamable HTTP from url. Use ~/.cursor/mcp.json instead to make ReUI available in every project.

Sign in with ReUI

The first time Cursor calls a ReUI tool, a browser window opens to authorize the connection. Click "Sign in with ReUI" to complete the OAuth prompt. If you do not have an account yet, a free ReUI account is created for you right in that flow, so there is nothing to set up in advance.

For headless or CI use where no browser is available, create a personal token at Account → MCP and add it as an Authorization header on the same server entry. Cursor interpolates ${env:NAME} inside headers, so keep the token in your environment rather than in the file. The ReUI installer writes this same header shape, but only when REUI_LICENSE_KEY is set in your environment as it runs; a keyless install leaves the entry headerless:

.cursor/mcp.json

{
  "mcpServers": {
    "reui": {
      "url": "https://mcp.reui.io",
      "headers": {
        "Authorization": "Bearer ${env:REUI_LICENSE_KEY}"
      }
    }
  }
}

This header is an alternative to the browser sign-in, not an addition to it. It is sent on every request and takes precedence over any OAuth credential the client has stored, so leave it out entirely on the sign-in path - otherwise authenticating appears to succeed while every call keeps failing.

Then export REUI_LICENSE_KEY=<your token or license key> in your shell profile. Pasting the literal reui_pat_... value works too, but only do that in a file you are not committing.

Install the ReUI skill

Run the one-line installer in your project so Cursor follows ReUI's build workflow:

Terminal

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

This drops a ReUI skill file into your project. Cursor reads it to learn how ReUI wants components discovered, assembled, and wired, so its output stays on the ReUI registry instead of freehand markup.

Build with ReUI

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

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 your environment, so leave it as a variable here. Cursor has its own syntax and only understands the env: prefix, so the MCP server entry above uses ${env:REUI_LICENSE_KEY}. Copying this bare ${REUI_LICENSE_KEY} form into .cursor/mcp.json sends it to ReUI as literal text and fails with a 401.

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

Most hiccups are a stale browser sign-in, and reconnecting fixes them. Cursor's MCP servers live under Customize in the sidebar, which is where you toggle, re-authorize, or remove reui. 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, open Customize, sign in to reui again, then restart Cursor.
401 and you signed in through the browser - your ReUI session expired. To fix it, open Customize and sign in to reui again.
401 and you use a personal token (headless or CI) - the token has expired or been revoked. Signing in again will not help: that renews a browser session, not the Authorization header your config sends. Create a new token at Account → MCP and update the header or the environment variable it reads. 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 Customize, sign in to reui again, and retry your last prompt. For the underlying error, open the Output panel and select MCP Logs.
Sign-in appears to work but every call still 401s - check whether you have an Authorization header on the reui server entry. A configured credential is sent on every request and overrides the OAuth credential the sign-in stores, so while it is there opening Customize and signing in to reui again 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.
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.

Codex Grok

On This Page

Connect ReUI Install the ReUI skill Build with ReUI Unlock premium items Troubleshooting

Connect ReUI

Add the ReUI MCP server

Add the reui server to Cursor in one click. Cursor opens, shows the server, and asks you to confirm - approve it, then reload.

Add to Cursor

Prefer to set it up by hand? Add ReUI to .cursor/mcp.json in your project, then reload Cursor:

.cursor/mcp.json

{
  "mcpServers": {
    "reui": {
      "url": "https://mcp.reui.io"
    }
  }
}

A remote server needs no type field - Cursor infers Streamable HTTP from url. Use ~/.cursor/mcp.json instead to make ReUI available in every project.

Sign in with ReUI

.cursor/mcp.json

{
  "mcpServers": {
    "reui": {
      "url": "https://mcp.reui.io",
      "headers": {
        "Authorization": "Bearer ${env:REUI_LICENSE_KEY}"
      }
    }
  }
}

Then export REUI_LICENSE_KEY=<your token or license key> in your shell profile. Pasting the literal reui_pat_... value works too, but only do that in a file you are not committing.

Install the ReUI skill

Run the one-line installer in your project so Cursor follows ReUI's build workflow:

Terminal

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

Build with ReUI

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

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 - Cursor 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

Tools missing, greyed out, or "not connected" - the server did not finish connecting. To fix it, open Customize, sign in to reui again, then restart Cursor.

401 and you signed in through the browser - your ReUI session expired. To fix it, open Customize and sign in to reui again.

401 and you use a personal token (headless or CI) - the token has expired or been revoked. Signing in again will not help: that renews a browser session, not the Authorization header your config sends. Create a new token at Account → MCP and update the header or the environment variable it reads. 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 Customize, sign in to reui again, and retry your last prompt. For the underlying error, open the Output panel and select MCP Logs.

Sign-in appears to work but every call still 401s - check whether you have an Authorization header on the reui server entry. A configured credential is sent on every request and overrides the OAuth credential the sign-in stores, so while it is there opening Customize and signing in to reui again 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.

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.