migration_guide — Hex.pm MCP MCP Prompt
migration_guide
is one of 5 prompts on the
Hex.pm MCP
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke migration_guide from your client
- Claude Code Hex.pm MCP Prompt/migration_guide run in your project directory
- Claude Desktop Hex.pm MCP Prompt/migration_guide ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Hex.pm MCP Prompt/migration_guide ~/.cursor/mcp.json
- VS Code Hex.pm MCP Prompt/migration_guide .vscode/mcp.json
- Zed Hex.pm MCP Prompt/migration_guide ~/.config/zed/settings.json
- Windsurf Hex.pm MCP Prompt/migration_guide ~/.codeium/windsurf/mcp_config.json
- Cline Hex.pm MCP Prompt/migration_guide ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Hex.pm MCP Prompt/migration_guide ~/.gemini/settings.json
- Grok Hex.pm MCP Prompt/migration_guide .mcp.json (in your project root)
- ChatGPT Hex.pm MCP Prompt/migration_guide Settings → Connectors → Advanced → Developer mode
- Claude.ai Hex.pm MCP Prompt/migration_guide Settings → Connectors → Add custom connector
- LangChain Hex.pm MCP Prompt/migration_guide pip install langchain-mcp-adapters
Other prompts on this server
Hex.pm MCP 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.