Cursor Cronus UI get_design_context
How to: Cursor Cronus UI get_design_context
Add Cronus UI to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"cronus-ui": {
"url": "https://aicronus.com/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something get_design_context does. Cursor lists the server's tools on connect and calls get_design_context itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Cronus UI's identifier in your config matches the one above exactly.
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 get_design_context 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.