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