get_design_context — Cronus UI MCP Tool Read-only
get_design_context
(get design context) is one of 8 tools on the
Cronus UI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_design_context from your client
- Claude Code Cronus UI get_design_context run in your project directory
- Claude Desktop Cronus UI get_design_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cronus UI get_design_context ~/.cursor/mcp.json
- VS Code Cronus UI get_design_context .vscode/mcp.json
- Zed Cronus UI get_design_context ~/.config/zed/settings.json
- Windsurf Cronus UI get_design_context ~/.codeium/windsurf/mcp_config.json
- Cline Cronus UI get_design_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cronus UI get_design_context ~/.gemini/settings.json
- Grok Cronus UI get_design_context .mcp.json (in your project root)
- ChatGPT Cronus UI get_design_context Settings → Connectors → Advanced → Developer mode
- Claude.ai Cronus UI get_design_context Settings → Connectors → Add custom connector
- LangChain Cronus UI get_design_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cronus-ui https://aicronus.com/mcpOther tools on this server
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.