migrate_ui_icons — Digche Icons MCP Prompt

migrate_ui_icons is one of 1 prompt on the Digche Icons MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke migrate_ui_icons from your client

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

Digche Icons also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.