Skip to content

Cronus UI

by pedrogbraz · remote · local (npm) · no sign-in to list tools · v0.7.6 · published by GitHub user pedrogbraz

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

Changes · 1
CompareRegistry entry

8 tools: 1 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http cronus-ui https://aicronus.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 1Claude Code: ask
  • match_catalogTwo-query catalog match for low-context agents.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 7Claude Code: allow
  • 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 ite…No findings

    Why it is in this group

    • The name "get_component" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_design_contextReturn the Cronus UI visual taste file (DESIGN.md) for a theme × look.No findings

    Why it is in this group

    • The name "get_design_context" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_install_commandBuild the `npx cronus-ui add ...` command for one or more components/blocks.No findings

    Why it is in this group

    • The name "get_install_command" says "get": a word for reading.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_blocksList the installable Cronus UI blocks (registry items of type 'registry:block') — larger, composed sections such as hero, pricing, login, and dashboard.No findings

    Why it is in this group

    • The name "list_blocks" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • 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 findings

    Why it is in this group

    • The name "list_catalog" says "list": a word for reading.
    Description, as the server wrote it
    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.).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_componentsList the installable Cronus UI components (registry items of type 'registry:ui').No findings

    Why it is in this group

    • The name "list_components" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_registryFuzzy-search Cronus UI components and blocks by name (case-insensitive substring match).No findings

    Why it is in this group

    • The name "search_registry" says "search": a word for reading.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.7.6. Values in angle brackets are yours to fill in.

claude mcp add --transport http cronus-ui https://aicronus.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cronus-ui__list_components",
      "mcp__cronus-ui__list_blocks",
      "mcp__cronus-ui__list_catalog",
      "mcp__cronus-ui__search_registry",
      "mcp__cronus-ui__get_design_context",
      "mcp__cronus-ui__get_component",
      "mcp__cronus-ui__get_install_command"
    ],
    "ask": [
      "mcp__cronus-ui__match_catalog"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as cronus-ui. Review it before you use it.