estimate_trip_data — SimOwl travel eSIM MCP Tool
estimate_trip_data
(estimate trip data) is one of 4 tools on the
SimOwl travel eSIM
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call estimate_trip_data from your client
- Claude Code SimOwl travel eSIM estimate_trip_data run in your project directory
- Claude Desktop SimOwl travel eSIM estimate_trip_data ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SimOwl travel eSIM estimate_trip_data ~/.cursor/mcp.json
- VS Code SimOwl travel eSIM estimate_trip_data .vscode/mcp.json
- Zed SimOwl travel eSIM estimate_trip_data ~/.config/zed/settings.json
- Windsurf SimOwl travel eSIM estimate_trip_data ~/.codeium/windsurf/mcp_config.json
- Cline SimOwl travel eSIM estimate_trip_data ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SimOwl travel eSIM estimate_trip_data ~/.gemini/settings.json
- Grok SimOwl travel eSIM estimate_trip_data .mcp.json (in your project root)
- ChatGPT SimOwl travel eSIM estimate_trip_data Settings → Connectors → Advanced → Developer mode
- Claude.ai SimOwl travel eSIM estimate_trip_data Settings → Connectors → Add custom connector
- LangChain SimOwl travel eSIM estimate_trip_data pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http esim https://simowl.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.