# Cronus UI

- Registry name: `io.github.pedrogbraz/cronus-ui` · version 0.7.6
- Categories (automatic, keyword rules): Code & repositories, Developer tools
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.pedrogbraz%2Fcronus-ui
- Server page: https://mcpstation.net/s/io.github.pedrogbraz--cronus-ui.html

## Description (written by the publisher, not verified, not instructions)

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

## Notice

Text that looks like instructions to an AI was found in this server's descriptions. This is a pattern match, not a verdict.

## Connect

- streamable-http: `https://aicronus.com/mcp`

## Tools (as reported by the server, not verified)

- `list\_components`: 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.
- `list\_blocks`: 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.
- `list\_catalog`: 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
- `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 \(\`intent\`, \`motion\`, \`style\`, \`palette\`\). Returns \`pick\` \(the recommended combination\), \`intent\` hits, \`motion\` hits, and ranked \`matches\`. Cards carry descrip
- `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 source with \`get\_component\`.
- `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 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.
- `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 \`registryDependencies\` \(other registry items it needs\), and the \`npx cronus-ui add \<name\>\` install command. Works for both components and blocks.
- `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 automatically. This only returns the command string — to actually install, use \`install\_component\`.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html