beUI Pro MCP Proxy

Use the beUI Pro MCP Server via the proxy (streamable HTTP) — no upstream subscription credentials needed

Endpoint

All MCP clients connect to this address, using the distributed key as the Bearer credential.

text

https://proxy.collectui.pro/api/beui-mcp

Configure MCP client

beUI Pro MCP is streamable HTTP. Add the config below to your client,YOUR_KEY with your distributed key (prefix beui_mcp_)

.mcp.json（Cursor / VS Code / Claude Desktop）

json

{
  "mcpServers": {
    "beui": {
      "url": "https://proxy.collectui.pro/api/beui-mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_KEY>"
      }
    }
  }
}

Claude Code

bash

claude mcp add --transport http beui https://proxy.collectui.pro/api/beui-mcp --scope user -H "Authorization: Bearer <YOUR_KEY>"

Codex CLI

toml

# ~/.codex/config.toml
[mcp_servers.beui]
enabled = true
url = "https://proxy.collectui.pro/api/beui-mcp"
http_headers = { Authorization = "Bearer <YOUR_KEY>" }

Replace the YOUR_KEY placeholder with your distributed beui MCP key. Once configured, you can use beUI's list_components / search_components / get_component tools.

CLI install (shadcn)

Install commands returned by the MCP are rewritten to this proxy's endpoints: add both @beui (free) and @beui-pro (Pro) registries to components.json, and set BEUI_PRO_TOKEN in .env to the same key.

Registry configuration

@beui serves free components (no key); @beui-pro serves Pro components (via the pro/ path, Bearer key required). See the CLI install page for the full setup.

View beUI CLI install configuration →

FAQ

How do I get a key?

Contact CollectUI to get a beui MCP key (prefix beui_mcp_). One key can be used across multiple clients.

What if I get a 503 (upstream rate limited)?

It means the upstream is temporarily rate limiting or under maintenance, handled by ops — no action needed from you; retry later.