plan_trip — Bloomy eSIM MCP Prompt

plan_trip is one of 1 prompt on the Bloomy eSIM MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke plan_trip from your client

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

Bloomy eSIM 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 25 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.