All servers · Code & repositories
Cronus UI
io.github.pedrogbraz/cronus-ui · v0.7.6
Instruction-like text in descriptions
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | resources, tools |
| Tool definitions | 8 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Instruction-like text was found in get_design_context. This is a pattern match, not a verdict. What we look for
Description written by the publisher, not verified
Search, install, compose, add-page, and theme Cronus UI from the live registry.
Connect
streamable-http · https://aicronus.com/mcp
claude mcp add --transport http cronus-ui https://aicronus.com/mcp{
"mcpServers": {
"cronus-ui": {
"url": "https://aicronus.com/mcp"
}
}
}Tools as reported by the server
list_componentsList 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_blocksList 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_catalogReturn 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 + smoothmatch_catalogTwo-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 descripsearch_registryFuzzy-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_contextReturn 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_componentFetch 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_commandBuild 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`.
Repository · Website · JSON · Text for agents · Registry updated 2026-09-09