Kilo Code

Kilo Code speaks MCP over Streamable HTTP, so one config entry connects it to the ReUI registry and you can build UI from ReUI components, examples, and blocks without leaving your editor. The endpoint is the same everywhere, https://mcp.reui.io, and for the shared background (the tools, the plan limits, the sign-in flow) see the MCP server overview.

Connect ReUI

{
  "mcp": {
    "reui": {
      "type": "remote",
      "url": "https://mcp.reui.io",
      "enabled": true
    }
  }
}

Headless and CI

For runs where no browser prompt is possible, create a personal token at Account → MCP (it looks like reui_pat_...) and send it as a Bearer header instead of signing in:

{
  "mcp": {
    "reui": {
      "type": "remote",
      "url": "https://mcp.reui.io",
      "headers": {
        "Authorization": "Bearer reui_pat_your_token_here"
      },
      "enabled": true,
      "timeout": 15000
    }
  }
}

Kilo Code's docs show literal header values and document no variable substitution for this file, so paste the real token and keep the file out of version control. timeout is optional and in milliseconds. 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.

Tokens expire after 90 days by default (30, 60, 90 and 180 are offered, plus No expiry for pipelines that cannot rotate). Nothing warns you beforehand, so an expired token simply starts returning 401 and has to be replaced, not re-authenticated.

The ReUI skill

There is nothing to install. The build workflow rides on the MCP: once reui is connected, ask Kilo Code to call get_agent_skill and it loads the full ReUI workflow (the reuse-first rule and the find, read the real API, install, then adapt order) as a document. If a build drifts off-pattern, tell it to "follow the ReUI skill" to reload that workflow.

Skip the one-line installer used in other guides here. It writes skill directories (.claude/skills, .agents/skills) that Kilo Code does not read: its instruction files are AGENTS.md, CLAUDE.md, and CONTEXT.md, discovered at the project root and in parent directories, with ~/.config/kilo/AGENTS.md for a global one. If you want the workflow on disk, paste it into AGENTS.md rather than running the installer.

Build with ReUI

Describe the interface you want in plain language and Kilo Code 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 Kilo Code 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 - Kilo Code 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 the config shape or a stale credential. A browser sign-in can be renewed; a personal token has to be replaced.

• Tools missing, greyed out, or "not connected" - the server did not finish connecting. To fix it, confirm the entry sits under the mcp key with "type": "remote", check it is toggled on in Settings → MCP, then reload the window.
• 401 and you signed in through the browser - your ReUI session expired. To fix it, disable and re-enable reui in Settings → MCP so Kilo Code starts the OAuth flow again.
• 401 and you use a personal token - the token is missing, mistyped, expired, or revoked. Re-authenticating will not help, because the Authorization header is not a browser session. Create a new token at Account → MCP and paste it into the header. 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, toggle reui off and on in Settings → MCP and retry your last prompt. Raising timeout helps on a slow network.
• 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 disabling and re-enabling reui in Settings → MCP 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.