Der Cronus UI MCP-Server,
verbunden mit einem Klick.

list_components — List the installable Cronus UI components (registry items of type 'registry:ui'). Returns each component's name, a readable title, its npm a

list_blocks — List the installable Cronus UI blocks (registry items of type 'registry:block') — larger, composed sections such as hero, pricing, login, an

list_catalog — Return compact Hydra-ready cards for every component, block, variant, and template: name, short description, design style, palette, motion,

match_catalog — Two-query catalog match for low-context agents. Pass a free-text `query` (e.g. 'login page with smooth animation') and/or structured filters

search_registry — Fuzzy-search Cronus UI components and blocks by name (case-insensitive substring match). Use this to find the right item before fetching its

get_design_context — Return the Cronus UI visual taste file (DESIGN.md) for a theme × look. Use this before generating UI so the agent follows Aurora/Neutral dua

get_component — Fetch the full detail for a single Cronus UI component or block by name: its source file(s) (path + content), its npm `dependencies`, its `r

get_install_command — Build the `npx cronus-ui add ...` command for one or more components/blocks. The CLI resolves and installs each item's registry dependencies