Gemini CLI 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, a remote server over Streamable HTTP, so there is nothing to run locally.
Connect ReUI
Add the ReUI MCP server
Add the reui server to ~/.gemini/settings.json (every project) or to .gemini/settings.json in the project (this project only), then restart Gemini CLI. Type /mcp inside the CLI to see the server and its status.
{
"mcpServers": {
"reui": {
"httpUrl": "https://mcp.reui.io"
}
}
}Gemini CLI uses httpUrl for Streamable HTTP servers (url means the older SSE transport, which the ReUI server does not serve). Environment variables in the form $NAME are expanded when the settings load.
Sign in with ReUI
The first time Gemini CLI calls a ReUI tool it prompts you to authorize the server; a browser window opens for the OAuth flow. Click "Sign in with ReUI" to complete it.
For headless or CI use where no browser is available, create a personal token at Account → MCP and send it as an Authorization header instead:
{
"mcpServers": {
"reui": {
"httpUrl": "https://mcp.reui.io",
"headers": {
"Authorization": "Bearer $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 session, so remove it when you want the browser sign-in back. A ReUI license key works in the same header for licensed installs.
Install the ReUI skill
Run the one-line installer in your project so Gemini CLI follows the ReUI build workflow:
curl -fsSL https://mcp.reui.io/install | node -This drops a ReUI skill file into your project. Gemini CLI reads it to learn how ReUI wants components discovered, assembled and wired, so its output uses the real registry instead of a guess at it.
Build with ReUI
Describe the interface you want in plain language and Gemini CLI pulls the right ReUI components, examples and blocks from the registry, then wires them into your project. A few prompts to start with:
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.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 22 components and every c-* example) install with no license. To let Gemini CLI install premium blocks, icons, and templates too, grab a Pro or Ultimate license and add the key to your project:
Add your license key
Copy your key from Account → Licenses into .env.local at the project root:
REUI_LICENSE_KEY=your-license-key-hereAdd the @reui registry to 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. See License Setup for the full guide, including monorepos.
Troubleshooting
- Tools missing or the server shows as disconnected - the connection did not finish. Check the config file for a typo in the URL, then restart Gemini CLI.
- 401 after signing in through the browser - your ReUI session expired. Sign in to
reuiagain from the MCP panel. - 401 with a personal token - the token has expired or been revoked. Signing in again will not help: create a new token at Account → MCP and update the header.
- Sign-in works but every call still 401s - an
Authorizationheader on the server entry overrides the browser session. Remove it, or make sure it carries a valid token.