About UI Beats
UI Beats MCP server gives coding agents access to the UI Beats catalogue of animated React components. It lets an agent search components, read source and props, and install them without visiting the website.
Key features
- 01Search components by plain-language query or name
- 02Read props table and usage example
- 03Read complete component source code
- 04List all components grouped by category
- 05Generate shadcn install command and npm dependencies
Use cases
- 01Letting a coding agent find a component from a description
- 02Checking real props before writing JSX
- 03Installing a component and its npm packages automatically
MCP support
The server exposes four MCP tools to clients: search_components, get_component, list_components and get_install_command.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
4Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | Maximum number of results (default 10). |
| query | string | Yes | What the component should do, in plain words, or its exact name. |
| category | string | No | Restrict results to one category, e.g. 'card' or 'block'. Omit to search everything; list_components shows the current set. |
Details
From the project README@uibeats/mcp
MCP server for UI Beats. Lets a coding agent search the component catalogue, read a component's full source and props, and install it, without anyone opening the website.
Install
Claude Code:
claude mcp add uibeats -- npx -y @uibeats/mcp
Cursor, Windsurf, Claude Desktop and anything else that reads an
mcpServers block:
{
"mcpServers": {
"uibeats": {
"command": "npx",
"args": ["-y", "@uibeats/mcp"]
}
}
}
Tools
| Tool | What it does |
|---|---|
search_components | Rank the catalogue against a plain-language query or a name |
get_component | Full docs for one component: props table, usage example, complete source |
list_components | Everything available, grouped by category |
get_install_command | The exact shadcn command, plus the npm packages it pulls in |
A typical exchange: the agent calls search_components("card that flips"),
then get_component("flip-card") to read the real props before writing any
JSX, then get_install_command("flip-card") and runs it.
How it works
There is no backend. The server is a cached client over two static files the site already publishes:
/r/components.json: the search index (names, descriptions, props, guidance)/docs/<category>/<name>.md: the canonical document for one component
The catalogue is cached in memory for ten minutes, and a stale copy is kept as a fallback so a brief network failure does not break every tool call.
Configuration
| Variable | Default | Purpose |
|---|---|---|
UIBEATS_URL | https://uibeats.com | Point at a local next dev while working |
UIBEATS_URL=http://localhost:3000 npx @uibeats/mcp
Development
This package is standalone: it is not part of the site's Yarn install.
cd packages/mcp
npm install
npm run build
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.