beUI Pro

Use the customer's live licensed beUI Pro catalog as the source of truth. Discover current items at runtime, install only the blocks the project needs, then compose and adapt the source.

Choose an access path

Follow the current agent access documentation for connection instructions.

• MCP: Use an existing authenticated connection to https://mcp.beui.dev/pro/mcp. OAuth-capable clients open beUI's approval page, where the user enters their license key. Clients with custom headers can also use bearer authentication. A working MCP connection does not require a separate token in the agent's shell.
• Direct registry or shadcn CLI: Follow the installation documentation. This path requires BEUI_PRO_TOKEN in the command environment and private registry configuration for namespaced CLI commands.

Prefer an available authenticated MCP connection. Do not replace it with token setup just because the shell has no token.

Protect access