MCP Server

Use UI Beats from inside your coding agent.

Most components now get chosen by whatever is writing the code, not by someone browsing a gallery. The UI Beats MCP server puts the whole catalogue (55 components, their props and their source) inside Claude Code, Cursor, Windsurf, or any other client that speaks MCP. Your agent can then find the right component and read its real props instead of guessing at an API.

Install

One click for Cursor and VS Code, one command for Claude Code, a config block for everything else.

Add to Cursor Add to VS Code

claude mcp add uibeats -- npx -y @uibeats/mcp

For Windsurf, Claude Desktop and anything else that reads an mcpServers block:

mcp.json

{
  "mcpServers": {
    "uibeats": {
      "command": "npx",
      "args": ["-y", "@uibeats/mcp"]
    }
  }
}

Tools

Four, deliberately. Each one maps to a step your agent actually takes.

search_components: Rank the catalogue against a plain-language query ("a card that flips", "number counting up") or an exact name.
get_component: The full document for one component: description, when to use it, every prop, a runnable example and the complete source.
list_components: Everything available, grouped by category.
get_install_command: The exact shadcn command for a component, plus the npm packages it pulls in.

A typical exchange: the agent searches for what you described, reads the component’s real props before writing any JSX, then runs the install command in your project root.

Without an MCP client

The same content is served as plain markdown, for agents that only fetch URLs.

/llms.txt: The index: every component, one line each, linking to its markdown.
/llms-full.txt: Every component’s props and complete source, in one file.
/docs/<category>/<name>.md: Any component page as markdown. Add .md to its URL.
/r/components.json: The whole catalogue as JSON, with props and guidance. CORS is open.

Point an agent at a single component:

curl https://uibeats.com/docs/card/flip-card.md

Source

The server is open source and has no backend of its own.

It is a cached client over the two static files above, so it stays in step with the site automatically. Read it under packages/mcp. To develop against a local site, set UIBEATS_URL.