A side-by-side look at the AeroCell — Travel eSIM Search and Travel MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AeroCell — Travel eSIM Search for travel & transportation work over a hosted endpoint; choose Travel MCP for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
find_esim_plans, get_esim_plan, find_regional_esim_plans.search_travel_options, get_airport_info, compare_routes.Rows where the two servers differ are marked.
| Spec | A AeroCell — Travel eSIM Search | |
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 54/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 3 | 5 |
| Full listing | View AeroCell — Travel eSIM Search | View Travel MCP |
find_esim_plansFind current AeroCell travel eSIM plans for one country. Use a two-letter ISO country code. Provide both travel dates if known; plans covering the whole trip are returned by default. Optional data and USD price filters narrow results.get_esim_planGet current details and an AeroCell checkout link for a plan ID returned by find_esim_plans. Requires the same country code.find_regional_esim_plansFind live multi-country AeroCell bundles. Supply every itinerary country as a two-letter ISO code; only bundles listing all those countries are returned. Optionally select a named region. A region-only search returns bundles and their exact country coverage, which must be checked before recommending for an itinerary.search_travel_optionsPrimary travel search workflow for one origin-destination airport pair. Use when the user wants flight/trip options for a specific route; use compare_routes for multiple routes, build_booking_link only when route details are already known, and get_airport_info only to validate one airport. Read-only, no authentication, no booking side effects. return_date is optional; omit it for one-way trips. Responses include route metadata and may include commission-eligible external booking links.get_airport_infoLook up metadata for one airport by IATA code. Use to validate or explain a single airport code before route planning; use search_travel_options for an actual trip search and compare_routes for multiple origin-destination pairs. Read-only, no authentication, no external booking links, and no booking side effects.compare_routesCompare two or more airport route pairs side by side. Use when the user is choosing between alternate origins, destinations, or airports; use search_travel_options for one dated route and get_airport_info for a single airport lookup. Read-only, no authentication, no booking side effects. Responses may include commission-eligible external booking links for each route.build_booking_linkGenerate only an external booking link for an already chosen route. Use after route details are known or after compare_routes/search_travel_options; do not use as the first step when the user still needs search guidance. Read-only, no authentication, no booking completion, and no reservation side effects. The returned link may be commission-eligible and is disclosed in output.explain_travel_timingExplain general travel timing and logistics, including booking windows, airport arrival timing, layovers, and seasonal considerations. Use for advice questions like when to book or how early to arrive; use search_travel_options when the user wants route-specific flight search. Read-only, no authentication, no external booking link, and no booking side effects.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"aerocell-travel-esim-search": {
"url": "https://aerocell.app/mcp"
}
}
}
{
"mcpServers": {
"forgemeshlabs-travel-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/travel-assistant-mcp"
]
}
}
}