# Cronus UI (npm · cronus-ui-mcp)

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

- Trust score: 77/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `aicronus.com`: 74/100, [markdown](https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus.md), [page](https://verifymcp.io/servers/pedrogbraz-cronus-ui/aicronus)
- npm · `cronus-ui-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp.md), [page](https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp)

## Channel facts

- Registry: `npm`
- Package: `cronus-ui-mcp`
- Version: `0.7.6`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2498 tokens (~156/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Cronus UI MCP server?

Cronus UI runs locally as an npm package, launched with npx -y cronus-ui-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pedrogbraz-cronus-ui -- npx -y cronus-ui-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "pedrogbraz-cronus-ui": {
      "command": "npx",
      "args": [
        "-y",
        "cronus-ui-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pedrogbraz-cronus-ui": {
      "command": "npx",
      "args": [
        "-y",
        "cronus-ui-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pedrogbraz-cronus-ui -- npx -y cronus-ui-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pedrogbraz-cronus-ui": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cronus-ui-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pedrogbraz-cronus-ui --command npx --arg -y --arg cronus-ui-mcp
```

### Hermes

```yaml
mcp_servers:
  pedrogbraz-cronus-ui:
    command: "npx"
    args: ["-y", "cronus-ui-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pedrogbraz-cronus-ui": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "cronus-ui-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pedrogbraz-cronus-ui -t stdio -c npx -a -y cronus-ui-mcp
```

### Other

```json
{
  "mcpServers": {
    "pedrogbraz-cronus-ui": {
      "command": "npx",
      "args": [
        "-y",
        "cronus-ui-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 76, +4)

- [functional improvement] Stability: unverified → 0.30

### 2026-09-09 (score 72)

First indexed and scored.

## MCP tools (14)

### `list_components` (~59 tokens)

List Cronus UI 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` (~66 tokens)

List Cronus UI 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` (~96 tokens)

List the tagged Cronus UI 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 animation, etc.).

Input parameters:

- `kind` (string): Restrict to component, block, variant, or template cards.

### `match_catalog` (~257 tokens)

Match Cronus UI catalog tags

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.

Input parameters:

- `intent` (string): Use-case intent: login, signup, pricing, dashboard, chart, form, …
- `kind` (string): Restrict to component, block, variant, or template.
- `limit` (integer): Max hits per list. Default 8.
- `motion` (string): Motion: none, snappy, smooth, cinematic.
- `palette` (string): Palette: semantic (follows theme), aurora, neutral, midnight, sunset, emerald.
- `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.

### `search_registry` (~67 tokens)

Search the Cronus UI 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`.

Input parameters:

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

### `get_design_context` (~139 tokens)

Get Cronus UI DESIGN.md taste

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.

Input parameters:

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

### `get_component` (~99 tokens)

Get a Cronus UI component or block

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.

Input parameters:

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

### `get_install_command` (~84 tokens)

Build a Cronus UI 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`.

Input parameters:

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

### `install_component` (~232 tokens)

Install Cronus UI components into the project

MODIFIES THE FILESYSTEM. Install one or more Cronus UI components/blocks into the current project by running the version-pinned `cronus-ui add` CLI at the detected project root (nearest directory with cronus-ui.json, else package.json). It writes the component source files, pulls in their registry dependencies, and installs their npm packages with the project's package manager. Use this — not a shell command — whenever the user asks to add/install a Cronus UI component or block. Existing files are skipped unless `overwrite` is true (overwrite discards local edits to those files). Requires a project initialised with `npx cronus-ui init`.

Input parameters:

- `names` (array, required): Registry item names to install, e.g. ['button', 'card'] or ['pricing']. Registry dependencies are resolved automatically.
- `overwrite` (boolean): Overwrite files that already exist in the project (destroys local edits to those files). Default: existing files are skipped.
- `skipInstall` (boolean): Write the source files but skip the package-manager install of npm dependencies; the result then lists them as pending.

### `upgrade_components` (~315 tokens)

Upgrade installed Cronus UI components and composed pages

MODIFIES THE FILESYSTEM. Upgrade installed Cronus UI components and composed pages/layouts to the current registry release by running the version-pinned `cronus-ui upgrade` CLI at the detected project root. 3-way merge of installed items AND composed pages/layouts so local edits survive. Prefer this over install_component overwrite and over compose --overwrite. dryRun first is recommended. Defaults to `--all` when `names` is omitted (the usual "pull latest" request). Pass `manifest` for custom compose apps. Requires a project initialised with `npx cronus-ui init`.

Input parameters:

- `all` (boolean): Upgrade every installed component and composed pages/layouts (`--all`). Default when `names` is empty. Set false only when passing `names`.
- `dryRun` (boolean): Preview the per-file plan (fast-forward / merge / conflict) without writing.
- `manifest` (string): Path to the compose manifest file (`--manifest`). Required when the app was composed from a custom `--manifest` whose name collides with a bundled template (or is not a bundled template).
- `names` (array): Registry item names to upgrade, e.g. ['button', 'card']. Omit (and leave `all` unset or true) to upgrade every installed component and composed pages/layouts. Named upgrades do not touch pages.
- `yes` (boolean): Pass `-y`: write conflict markers and confirmed overwrites without asking. Unlike compose_app, this does not default to true.

### `apply_theme` (~169 tokens)

Apply a Cronus UI theme to the project

MODIFIES THE FILESYSTEM. Apply a theme built in the Cronus UI Create Studio to the current project by running the version-pinned `cronus-ui theme add` CLI at the detected project root. It updates the app layout's theme attributes, writes the theme override block into the global stylesheet (replacing any previous one), and records the theme in cronus-ui.json. Use this when the user provides a Create Studio permalink or an exported theme JSON file and wants it applied. Set `dryRun` to preview the changes without writing anything.

Input parameters:

- `dryRun` (boolean): Preview what would change without writing any files.
- `source` (string, required): The theme to apply: a Create Studio permalink URL, a bare `c=` payload, or a path to an exported theme JSON file.

### `compose_app` (~315 tokens)

Compose a Cronus UI app from a template

MODIFIES THE FILESYSTEM. Generate a full multi-page app from a validated Cronus UI template (saas, store, landing, landing-*, mail, chat, finance) by running the version-pinned `cronus-ui compose` CLI at the detected project root. Prefer this over hand-writing pages: it installs the template's blocks, writes route files that only stack those blocks in <main>, and records the app in cronus-ui.json. Use when the user wants a full product, not a single primitive. Set `dryRun` to preview without writing. Requires a project initialised with `npx cronus-ui init` — this does not scaffold a new app (use `npx create-cronus-app` for greenfield).

Input parameters:

- `brand` (string): Brand wordmark baked into chrome/hero. Ignored when empty.
- `dryRun` (boolean): Preview the validated plan without writing any files.
- `overwrite` (boolean): Overwrite files that already exist (`--overwrite`).
- `skipInstall` (boolean): Write the files but skip the package-manager install of npm dependencies.
- `template` (string, required): Bundled app template (saas, store, landing, landing-*, mail, chat, finance).
- `variant` (array): Block variant selections as slug=id tokens, e.g. ['login=split']. Each becomes `--variant <token>`.
- `yes` (boolean): Pass `-y` (non-interactive). Defaults to true so agents never hang.

### `add_page` (~358 tokens)

Add a page to a composed Cronus UI app

MODIFIES THE FILESYSTEM. Grow an already-composed app by one page: install the named blocks, write a generated page that stacks them in <main>, and update the chrome nav + composed record. Runs the version-pinned `cronus-ui add-page` CLI at the detected project root. Use after `compose_app` when the user wants a new route. Set `dryRun` to preview without writing. Pass `app` (`--app`) when the project has more than one composed app. Pass `manifest` when the app was composed from a custom `--manifest`.

Input parameters:

- `app` (string): Composed app key (`--app`). Required when the project has more than one composed app.
- `blocks` (string, required): Comma-separated block slugs to stack, e.g. 'pricing,cta'. Variant syntax 'login=split' is allowed.
- `chrome` (string): Chrome group for the page (default: the app's first group).
- `dryRun` (boolean): Preview the plan without writing any files.
- `manifest` (string): Path to the compose manifest file (`--manifest`). Required when the app was composed from a custom `--manifest` whose name collides with a bundled template (or is not a bundled template).
- `nav` (string): Nav label; adds the page to the chrome nav.
- `overwrite` (boolean): Replace the page if the route already exists (`--overwrite`).
- `route` (string, required): Route to add, starting with '/', e.g. '/pricing'.
- `skipInstall` (boolean): Write the files but skip the package-manager install of npm dependencies.
- `title` (string): Page <title> (default: title-cased route).

### `set_theme` (~137 tokens)

Set the Cronus UI theme preset

MODIFIES THE FILESYSTEM. Switch the baked-in Cronus UI theme preset (and optionally the color mode) by running the version-pinned `cronus-ui theme set` CLI at the detected project root. Use this for aurora / neutral / midnight / sunset / emerald. For Create Studio permalinks or exported JSON, use `apply_theme` instead.

Input parameters:

- `mode` (string): Color mode to pin ('dark' or 'light'). Omitting leaves the current mode.
- `name` (string, required): Baked-in preset: 'aurora', 'neutral', 'midnight', 'sunset', or 'emerald'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp#diagnostics

## Score history

- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 72

## Common questions

### What is the Cronus UI MCP server?

Cronus UI is an MCP server listed in the public MCP registry as io.github.pedrogbraz/cronus-ui. Search, install, compose, add-page, and theme Cronus UI from the live registry. This page covers its npm package (cronus-ui-mcp).

### Is the Cronus UI MCP server safe to use?

Cronus UI scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Cronus UI MCP server expose?

Cronus UI exposes 14 tools: list_components, list_blocks, list_catalog, match_catalog, search_registry, and 9 more. Their descriptions and schemas cost roughly 2,393 tokens of context every time the server is loaded.

### Is the Cronus UI MCP server still maintained?

Cronus UI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Cronus UI MCP server under?

Cronus UI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/cronus-ui-mcp
- Socket report: https://socket.dev/npm/package/cronus-ui-mcp
- Repository: https://github.com/pedrogbraz/cronus-ui
- Website: https://aicronus.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pedrogbraz-cronus-ui/cronus-ui-mcp