Skip to content

Cline Cronus UI list_components

How to: Cline Cronus UI list_components

client:Cline transport:streamable-http tool:list_components

Add Cronus UI to Cline

  1. 01

    Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "cronus-ui": {
      "url": "https://aicronus.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cline.

  2. 03

    Ask for something list_components does. Cline lists the server's tools on connect and calls list_components itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Cronus UI's identifier in your config matches the one above exactly.

Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs

Set these first

Cronus UI will not start until these are set, so list_components never becomes available.

  • CRONUS_UI_REGISTRY
  • CRONUS_MCP_CLI_CMD
  • CRONUS_MCP_CLI_TIMEOUT_MS

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.