trip_plan — HemmaBo Host Booking Engine MCP Prompt

trip_plan is one of 2 prompts on the HemmaBo Host Booking Engine MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke trip_plan from your client

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

Other prompts on this server

• host_start

HemmaBo Host Booking Engine 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.