The ReUI MCP server puts the live ReUI registry inside your coding agent - scored search, real component APIs, and exact install commands over one endpoint.
The ReUI MCP server connects your coding agent to the live ReUI registry. Through one endpoint your agent searches the full library with scored, intent-based matching, reads real component APIs, and gets exact shadcn CLI install commands - so it ships real ReUI instead of guessing.
Endpoint
https://mcp.reui.io
The server runs over Streamable HTTP and works with any MCP-capable agent. It is free with a ReUI account: the first connection opens a "Sign in with ReUI" approval in your browser, and a free account is created in that flow if you do not have one.
The tools
Every tool answers against the current registry, scored and ranked.
Find
search - ranked matches across components, examples, blocks, and icons for a natural-language query, each with an install command, live preview, docs link, and the components it uses.
search_icons - the best-matching icon for many concepts ("save", "user settings") in one call, optionally pinned to one icon style.
list_components - the 19 free ReUI building blocks (data-grid, event-calendar, gantt, kanban, filters, ...).
list_block_groups - the top-level block groups (application, ecommerce, marketing, ...) with counts.
list_block_categories, list_example_categories, list_icon_categories - the categories of each type with item counts, for narrowing a search.
Read
get_component - the inline API (props and usage) for one or many components in a single call, so props come from the docs, never from memory.
get_examples - a component's real, working example compositions to copy instead of hand-rolling.
get_block, get_example, get_icon - full metadata for one item by name: description, components used, dependencies, install command, docs and preview links.
Plan and validate
compose_page - turns a whole-page intent into ordered sections, each matched to the best block for the job.
validate_usage - checks planned components and props against the documented API before any code is written.
get_audit_checklist - the ReUI-specific checks to run after installing and adapting an item.
Install and unlock
get_install_command - the exact shadcn CLI command for an item, validated against the registry (wrong names get did-you-mean suggestions, not a fabricated command).
get_project_context - the components.json registry config and license-key setup so shadcn add @reui/... works.
get_agent_skill - the full ReUI build skill, served at runtime to agents that cannot install files.
Connect in three steps
The flow is the same in every agent; only where you paste the endpoint differs.
Add the server
Register https://mcp.reui.io as an HTTP MCP server wherever your agent configures MCP - a one-line command in local CLIs and editors, a connector or integrations screen in hosted services. The per-agent guides below have the exact command or settings path for each.
Sign in with ReUI
On the first connection your agent opens the "Sign in with ReUI" approval in your browser - a free ReUI account is created in that flow if you do not have one. For runs without a browser (CI, remote sessions), create a personal token at your account and pass it as a Bearer header instead: Authorization: Bearer reui_pat_... with the token pasted in. A header value is sent exactly as written, so the ${REUI_LICENSE_KEY} form used in components.json, which the shadcn CLI expands, would arrive here as literal text and fail with a 401.
Build
Describe the interface you want in plain language. Pair the server with the Agent Skill so your agent follows the full ReUI workflow: find, install, read the API, adapt by reuse.
Free covers components and examples at 100 requests per day. A Pro or
Ultimate license unlocks premium blocks and animated icons and
removes the daily limit - add the @reui registry via License
Setup to install the premium items it returns.