For AI coding agents (MCP server)

How to set up the MCP server that lets Claude Code, Cursor, and Codex search WebberUI components and fetch their source and install commands directly.

WebberUI ships an MCP server (@webberui/mcp) that lets an AI coding agent search components and fetch their source and install commands without reading the docs first.

Read this first: you may not need it

Since shadcn CLI 4.13 there is a built-in MCP server, and it is more complete than this one:

npx shadcn@latest mcp

Once registries is configured in components.json (see Installing Pro components), it provides tools such as search_items_in_registries, view_items_in_registries, and get_add_command_for_items, which cover most needs. If your project already has a components.json, use the official one.

@webberui/mcp solves exactly one problem: those official tools all require the project to already have a components.json, so in an empty project that has not been inited you cannot ask them anything. This server does not depend on components.json, so you can explore first, get the install command, and then decide whether to init.

Setup

claude mcp add webberui \
  -e WEBBERUI_URL=https://webberui.com \
  -e WEBBERUI_KEY=<your Pro license key, optional> \
  -- npx -y @webberui/mcp

Environment variable	Default	Description
`WEBBERUI_URL`	`https://webberui.com`	Base URL of the registry
`WEBBERUI_KEY`	(none)	Pro license key. Search and browsing of every item work without it; the only difference is that fetching Pro source returns a purchase message instead of the code

Tools provided

Tool	Description
`search_components`	Search by name / title / description / category, optionally restricted to Free or Pro
`get_component`	Get a single item's install command, npm dependencies, and complete source
`list_categories`	List every category and its count
`list_templates`	List the full-page templates (always Pro)

The catalog is fetched live from /r/registry.json rather than bundled as a static snapshot — new components are visible immediately, with no need to update this package.

Usage (just tell the agent)

"Use webberui to find a card component with a glowing border and install it"

The agent goes: search_components("border") → picks border-beam → get_component("border-beam") to get the install command and source → runs the install.

Behavior for unlicensed Pro items

Without a license, get_component does not return blank or guessed code. It clearly reports that this is a Pro item, gives the purchase link, and instructs the agent not to reimplement it on its own.

That is deliberate: silently returning an empty string makes the agent think the component is empty and then invent one — that was the behavior in 1.0.0, and it has been fixed.

Pro is free during the campaign

During the launch campaign, registering an account is enough to install every Pro item. See Installing Pro components for how to get a key and set it up.

Alternatives to using MCP

If you would rather not install an MCP server, these two URLs are machine-readable on their own:

https://webberui.com/r/registry.json — the complete index, 479 items, each tagged with meta.tier (free / pro)
https://webberui.com/llms.txt — a site index in llmstxt.org format, which can be pasted straight into an agent as a documentation source