Agent access

Use beUI Pro from your coding agent.

Give your agent the live Pro catalog, licensed source files, and exact install commands. Choose the reusable skill or connect directly over MCP.

Install the Agent Skill

Add the skill to a project that supports agent skills. It reads the current authenticated registry at runtime, selects only relevant blocks, and preserves your project's existing design system.

npx skills add starc007/ui-components --skill beui-pro

Get your license key

Connect the MCP server

Connect Claude with OAuth, or use your license key as a bearer token in clients that support custom headers.

Claude

Add the endpoint below as a custom connector in Claude. Select Connect, enter your beUI Pro license key on the approval page, then select Authorize. Claude completes the OAuth connection without receiving your license key.

Server URL

https://mcp.beui.dev/pro/mcp

Get your license key

Codex or Claude Code

Export BEUI_PRO_TOKEN, then run the command for your coding agent.

$ codex mcp add beui-pro --url https://mcp.beui.dev/pro/mcp --bearer-token-env-var BEUI_PRO_TOKEN

Bearer-token configuration

Use this configuration when your MCP client accepts custom authorization headers but does not support the OAuth flow.

JSONmcp.json

{
  "mcpServers": {
    "beui-pro": {
      "url": "https://mcp.beui.dev/pro/mcp",
      "headers": {
        "Authorization": "Bearer ${BEUI_PRO_TOKEN}"
      }
    }
  }
}

Endpoint

https://mcp.beui.dev/pro/mcp

Available tools

List, search, inspect source, install

Keep your key private

Store BEUI_PRO_TOKEN in your environment. Never paste it into source files, commit it, or pass it as an agent tool argument. When you connect with OAuth, enter the key only on the beUI Pro approval page. Your MCP client receives an access token, not the license key. Every access path fetches the current catalog instead of relying on a stale component list.