Skip to content

Cursor Cronus UI Resource/registry-index

How to: Cursor Cronus UI registry-index

client:Cursor transport:streamable-http resource:registry-index

Add Cronus UI to Cursor

  1. 01

    Open ~/.cursor/mcp.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 Cursor.

  2. 03

    registry-index is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

  3. 04

    If it does not appear, check that Cronus UI is connected and that you are looking at its resources rather than its tools.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

Cronus UI will not start until these are set, so it never reaches Cursor.

  • CRONUS_UI_REGISTRY
  • CRONUS_MCP_CLI_CMD
  • CRONUS_MCP_CLI_TIMEOUT_MS

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.