Search 109k UI components and 1,556 blocks with licence evidence. Ask before you ship.
Scored across 9 tools
The core split is clear: search_* for discovery, get_* for a single record, list_* for enumeration, and compose_page for orchestration. The one soft boundary is get_page, a generic Markdown fetcher that overlaps with get_component and get_block, and get_design_system vs list_design_systems which are easily confused on a skim. Descriptions do disambiguate each case, so misselection is unlikely but possible.
All nine tools follow a strict snake_case verb_noun pattern (compose_, get_, list_, search_). The verbs map cleanly to intent classes, giving a predictable mental model.
Nine tools for a catalogue/browsing server is well-scoped, with discovery, retrieval, and composition each represented without redundancy. Every tool has a distinct job; nothing feels padded or missing.
The surface covers the full browse-to-compose lifecycle: categories, component and block search, single-record reads, design tokens, and page composition. Minor gap: list_categories returns counts but there is no direct way to enumerate components within a category without falling back to search or get_page on the hub URL.
Compose a page from real catalogue blocks. Returns an ordered plan with block slugs, page URLs, dependencies and constraints, not generated code.
Inputs: intent (required), limit, theme, pageType, +1 more.
Read one block by source + name: description, file list, registry dependencies and where it is published.
Inputs: name (required), source (required).
Read one component by library + name: description, license, page URL and the install command.
Inputs: name (required), library (required).
Return design tokens (colours, typography, radius, shadows, spacing) plus agent instructions, so generated UI stays visually consistent. Call this before composing a page.
Inputs: slug.
Fetch any catalog page as Markdown (a component, a category hub, a library page, an article). Use the same paths as the site, e.g. /components/cat/modal or /blog.
Inputs: path (required).
List catalog categories with the number of components in each, so an agent can browse instead of guessing queries.
Inputs: no named parameters.
List the available design systems with one-line descriptions.
Inputs: no named parameters.
Search composed UI blocks (hero, pricing, navbar, blog, dashboard…). A block is a whole section published by its author as registry:block, not a single component. Returns the block page, its dependencies and the source registry.
Inputs: query (required), limit, source.
Search the EneUI catalog of React/Tailwind/shadcn components. Returns matching components with their page URL and the one-line shadcn install command.
Inputs: query (required), limit, library, category.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.