OpenCode

Connect OpenCode to ReUI in one step and build UI from the ReUI registry directly in 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

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reui": {
      "type": "remote",
      "url": "https://mcp.reui.io",
      "enabled": true
    }
  }
}

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reui": {
      "type": "remote",
      "url": "https://mcp.reui.io",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer reui_pat_your_token_here"
      }
    }
  }
}

Install the ReUI skill

OpenCode runs locally, so add the ReUI skill with a single command:

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

This drops a ReUI skill file into your project so OpenCode follows ReUI's build workflow (discovering components, pulling source, and assembling blocks the way ReUI intends) instead of guessing.

Build with ReUI

Describe the interface you want in plain language and OpenCode 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. To let OpenCode 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 - OpenCode 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. 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, run opencode mcp auth reui, then restart OpenCode.
• 401 and you signed in through the browser - your ReUI session expired. To fix it, run opencode mcp auth reui to sign in again. If it keeps failing, clear the stored credential with opencode mcp logout reui first.
• 401 and you use a personal token (headless or CI) - the token has expired or been revoked. opencode mcp auth will not help, because it renews the stored OAuth credential, not the Authorization header from your headers block. 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.
• opencode mcp auth reui keeps failing, or succeeds and the tools still 401 - check whether your opencode.json has a headers.Authorization entry. If it does, remove it and run the auth command again. That header is sent on every request and overrides the OAuth credential the sign-in just stored, so while it is present the browser flow cannot take effect. The two methods are alternatives; use the header only on the headless path, with no OAuth.
• Unexpected status: needs_auth, often with a saveDiscoveryState()/discoveryState() warning above it - this one is not a ReUI-side failure and re-running the auth command will not clear it. needs_auth is OpenCode's own status string, and the warning comes from its MCP SDK, which is mid-upgrade: OpenCode's OAuth provider has not implemented the SDK's newer discovery-state methods yet, so the browser sign-in can succeed while the CLI still reports itself as unauthenticated. Update OpenCode first, since this is actively being fixed upstream. If you are still stuck, skip the browser flow entirely: remove any stored OAuth credential, then use a personal token with the headers config shown above - that path does not touch OAuth and works today.
• Requests hang or the session drops mid-build - long sessions can lose the connection. To fix it, run opencode mcp auth reui and retry your last prompt.
• 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.