GitHub Copilot

GitHub Copilot connects to ReUI in one step, so you can build UI from the ReUI registry right inside your editor. The endpoint is the same everywhere, https://mcp.reui.io over Streamable HTTP, but Copilot configures MCP differently on each surface, so pick yours below. For the shared background (the tools, the plan limits, the sign-in flow) see the MCP server overview.

Connect ReUI

{
  "servers": {
    "reui": {
      "type": "http",
      "url": "https://mcp.reui.io"
    }
  }
}

{
  "servers": {
    "reui": {
      "type": "http",
      "url": "https://mcp.reui.io",
      "headers": {
        "Authorization": "Bearer reui_pat_your_token_here"
      }
    }
  }
}

{
  "mcpServers": {
    "reui": {
      "type": "http",
      "url": "https://mcp.reui.io",
      "headers": {
        "Authorization": "Bearer reui_pat_your_token_here"
      },
      "tools": ["*"]
    }
  }
}

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

{
  "servers": {
    "reui": {
      "url": "https://mcp.reui.io",
      "requestInit": {
        "headers": {
          "Authorization": "Bearer reui_pat_your_token_here"
        }
      }
    }
  }
}

The ReUI skill

Run this one-liner in your project root:

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

It writes the ReUI skill to .claude/skills/reui and .agents/skills/reui, both of which VS Code Copilot loads as project skills (alongside .github/skills), so your agent follows ReUI's build workflow (picking the right blocks, wiring components, keeping the registry conventions) instead of guessing. The same run adds ReUI's design rules to AGENTS.md (never created beside a CLAUDE.md) and writes the skill and MCP entry of the other agents it supports, including a reui entry in ~/.codex/config.toml in your home directory. Add REUI_DRY_RUN=1 before node to see every planned write first.

If a surface does not read those folders, nothing is lost: the same workflow ships with the server, and Copilot can pull it any time by calling the get_agent_skill tool.

Build with ReUI

Describe the interface you want in plain language and GitHub Copilot 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 27 components and every c-* example) install with no license. To let Copilot install premium blocks and icons 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 - Copilot 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

In VS Code most hiccups are a stale browser sign-in, and reconnecting fixes them. On the CLI and in JetBrains, Eclipse, or Xcode you are on 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 MCP: List Servers in VS Code and restart reui (on the CLI, run /mcp and check the server is enabled), then restart your editor. If you are on a Business or Enterprise plan, confirm the MCP servers in Copilot policy is enabled.
• 401 and you sign in through VS Code - your ReUI session expired. To fix it, run MCP: List Servers and re-authenticate reui.
• 401 and you use a personal token (CLI, JetBrains, Eclipse, Xcode, CI) - the token has expired or been revoked. Re-authenticating will not help, because the Authorization header your config sends is not a browser session. Create a new token at Account → MCP and update 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, restart the reui server from MCP: List Servers (or /mcp on the CLI) and retry your last prompt.
• 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 running MCP: List Servers and re-authenticating reui 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.
• "Your free ReUI MCP allowance ... is used up" in a tool result - the free plan has a daily MCP request allowance and today's is used up. It arrives as a normal tool result Copilot shows you, not an HTTP error, so there is no status code to look for, and it resets at UTC midnight. For unlimited requests use a Pro or Ultimate license key, or a personal token from a licensed account, as your MCP credential, or wait for the reset.
• 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.

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.