Cronus UI
Server Details
Search, install, compose, add-page, and theme Cronus UI from the live registry.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- pedrogbraz/cronus-ui
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Most tools are clearly distinct: get_component fetches source, get_design_context returns taste rules, and search_registry/match_catalog handle discovery. There is some overlap between list_catalog and list_blocks/list_components, but descriptions clarify their different levels of detail and filtering.
All tools follow consistent lower_snake_case verb_noun naming: get_*, list_*, search_*, match_*. The pattern is predictable and easy to infer across the whole toolset.
Eight tools is well-scoped for a UI registry: discovery, search, matching, detail retrieval, design context, and install command generation. Each tool contributes a distinct function without redundancy.
The set covers discovery and retrieval well, but get_install_command explicitly references a non-existent install_component tool, creating a clear dead end. Additionally, templates and variants are listed in the catalog but cannot be fetched via get_component.
Available Tools
8 toolsget_componentGet a Cronus UI component or blockARead-onlyInspect
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.
Inputs: name (required).
get_design_contextGet Cronus UI DESIGN.md tasteARead-onlyInspect
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.
Inputs: look, theme, format.
get_install_commandBuild a Cronus UI install commandARead-onlyInspect
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.
Inputs: names (required).
list_blocksList Cronus UI blocksARead-onlyInspect
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.
Inputs: no named parameters.
list_catalogList the tagged Cronus UI catalogARead-onlyInspect
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.).
Inputs: kind.
list_componentsList Cronus UI componentsARead-onlyInspect
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.
Inputs: no named parameters.
match_catalogMatch Cronus UI catalog tagsARead-onlyInspect
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.
Inputs: kind, limit, query, style, +3 more.
search_registrySearch the Cronus UI registryARead-onlyInspect
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.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search, read and add Frontic UI's Vue components for commerce storefronts.
Search, read and install agent-ready React components, screens and blocks for AI products.
Search the Foundry44 library and install animated UI components for any stack.
Find UI components and themes, retrieve code, and generate with hosted 21st AI when enabled.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceSearch, inspect and install the 21 free MIT components of Marvelous UI (framework-agnostic Web Components and CSS) and their design tokens into a project. Runs locally over stdio with no network calls.1MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to browse, customize, and compose UI components, design tokens, site content, and a UI/UX spec into standalone pages. Also supports searching components and retrieving specs, resources, and prompts for page generation.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to search and extract design themes, review UI source with deterministic rules, and install shadcn-compatible React/Radix components from a local registry. Provides editable guidance topics and rendered spacing evidence without requiring an account for public catalog, guidance, and review calls.1MIT
- AlicenseBqualityBmaintenanceEnables any MCP client to search, read, and install free Aura components, agent skills, images/clips, and DESIGN.md systems straight from the public catalogue over stdio, with no account, OAuth, or API key needed. It also returns install plans, token starters, starter kits, and trending/category data so agents can assemble landing pages and UI sections in a few calls.3540 npm6MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.