bloomy_plan_cards — Bloomy eSIM MCP Resource

bloomy_plan_cards is one of 1 resource on the Bloomy eSIM MCP server. Connect the server and your client can attach it as context.

by client

How to attach bloomy_plan_cards from your client

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

Bloomy eSIM also offers 1 prompt — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 25 September 2026. A listing does not declare its resources, 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 resource's type and contents.