Cronus UI

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Search, install, compose, add-page, and theme Cronus UI from the live registry.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Cronus UI": {
      "url": "https://aicronus.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (8)

• list_components read-only

  List the installable Cronus UI components (registry items of type 'registry:ui'). Returns each component's name, a readable title, its npm and registry dependencies, and the `npx cronus-ui add <name>` command to install it.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• list_blocks read-only

  List the installable Cronus UI blocks (registry items of type 'registry:block') — larger, composed sections such as hero, pricing, login, and dashboard. Returns each block's name, title, dependencies, and its `npx cronus-ui add <name>` install command.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• list_catalog read-only

  Return compact Hydra-ready cards for every component, block, variant, and template: name, short description, design style, palette, motion, intents, and the install command. No source files — cheap on tokens. Filter with `kind`. Use `match_catalog` to pick the best item for a prompt (login + smooth animation, etc.).

  Parameters:

  • kind — string — Restrict to component, block, variant, or template cards.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• match_catalog read-only

  Two-query catalog match for low-context agents. Pass a free-text `query` (e.g. 'login page with smooth animation') and/or structured filters (`intent`, `motion`, `style`, `palette`). Returns `pick` (the recommended combination), `intent` hits, `motion` hits, and ranked `matches`. Cards carry description, design style, palette, motion, and intents — not source. Fetch source with `get_component` only after picking a name.

  Parameters:

  • kind — string — Restrict to component, block, variant, or template.
  • limit — integer — Max hits per list. Default 8.
  • query — string — Natural-language request, e.g. 'login page with smooth animation'. Intent and motion are inferred from the text when those fields are omitted.
  • style — string — Design style: default, editorial, operational, glass, brutalist.
  • intent — string — Use-case intent: login, signup, pricing, dashboard, chart, form, …
  • motion — string — Motion: none, snappy, smooth, cinematic.
  • palette — string — Palette: semantic (follows theme), aurora, neutral, midnight, sunset, emerald.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• search_registry read-only

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

  Parameters:

  • query (required) — string — Search text matched against component and block names, e.g. 'button' or 'card'.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• get_design_context read-only

  Return the Cronus UI visual taste file (DESIGN.md) for a theme × look. Use this before generating UI so the agent follows Aurora/Neutral dual identity, one primary CTA, hairline elevation, and look rules. compact fits a system prompt; extended is the repo file. Does not modify the project.

  Parameters:

  • look — string — Material: default, brutalist, or glass. Orthogonal to theme.
  • theme — string — Palette: aurora (generated product), neutral (docs chrome), midnight, sunset, emerald.
  • format — string — compact (~prompt) or extended (full DESIGN.md). Default extended.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• get_component read-only

  Fetch the full detail for a single Cronus UI component or block by name: its source file(s) (path + content), its npm `dependencies`, its `registryDependencies` (other registry items it needs), and the `npx cronus-ui add <name>` install command. Works for both components and blocks.

  Parameters:

  • name (required) — string — The exact registry item name, e.g. 'button', 'data-table', or 'pricing'.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• get_install_command read-only

  Build the `npx cronus-ui add ...` command for one or more components/blocks. The CLI resolves and installs each item's registry dependencies automatically. This only returns the command string — to actually install, use `install_component`.

  Parameters:

  • names (required) — array — One or more registry item names to install, e.g. ['button', 'card', 'dialog'].

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.