registry-index — Cronus UI MCP Resource

registry-index is one of 2 resources on the Cronus UI MCP server. Connect the server and your client can attach it as context.

by client

How to attach registry-index from your client

• Claude Code Cronus UI Resource/registry-index run in your project directory
• Claude Desktop Cronus UI Resource/registry-index ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Cronus UI Resource/registry-index ~/.cursor/mcp.json
• VS Code Cronus UI Resource/registry-index .vscode/mcp.json
• Zed Cronus UI Resource/registry-index ~/.config/zed/settings.json
• Windsurf Cronus UI Resource/registry-index ~/.codeium/windsurf/mcp_config.json
• Cline Cronus UI Resource/registry-index ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Cronus UI Resource/registry-index ~/.gemini/settings.json
• Grok Cronus UI Resource/registry-index .mcp.json (in your project root)
• ChatGPT Cronus UI Resource/registry-index Settings → Connectors → Advanced → Developer mode
• Claude.ai Cronus UI Resource/registry-index Settings → Connectors → Add custom connector
• LangChain Cronus UI Resource/registry-index pip install langchain-mcp-adapters

Other resources on this server

• catalog-tags

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.