Zed

Zed connects to ReUI as a context server, so you can build UI from the ReUI registry right inside the assistant panel. 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

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

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

The ReUI skill

You do not install a separate skill - it rides on the MCP from mcp.reui.io. Once ReUI is connected, Zed gets the ReUI tools and can call get_agent_skill to load the full build workflow (the reuse-first rule and the find, read the real API, install, then adapt order) as a document. If a build ever drifts off-pattern, tell it to "follow the ReUI skill" to reload that workflow.

Build with ReUI

Describe the interface you want in plain language and Zed 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 Zed 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 - Zed 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. Zed's servers live under Settings > AI > MCP Servers (the agent: open settings action gets you there too). 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 Settings > AI > MCP Servers, re-authenticate reui, then restart Zed.
• 401 and you signed in through the browser - your ReUI session expired. To fix it, open Settings > AI > MCP Servers and re-authenticate reui.
• 401 and you use a personal token (headless or CI) - the token has expired or been revoked. Re-authenticating will not help, and Zed will not even offer it while an Authorization header is set on the entry. Create a new token at Account → MCP and replace the header value. 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, re-authenticate reui from Settings > AI > MCP Servers 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 the browser sign-in prompt, which Zed only shows when no header is configured 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.