A side-by-side look at the AeroCell — Travel eSIM Search and Gingerguide City Catalog 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 Gingerguide City Catalog 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_attractions, find_nearby_attractions, get_attraction.Rows where the two servers differ are marked.
| Spec | A AeroCell — Travel eSIM Search | |
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 54/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 13 |
| Full listing | View AeroCell — Travel eSIM Search | View Gingerguide City Catalog |
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_attractionsSearches sights in all cities or in one city, by free text, category, interest, historical period, indoor or outdoor, visit length, or distance from a point. Example: five Byzantine sights in Istanbul.find_nearby_attractionsReturns the sights closest to a latitude and longitude, with walking minutes. If no sight is in the radius, it returns the nearest covered city.get_attractionReturns one sight: long description, a notable fact, photo, coordinates, map link, visit time and the nearest other sights.search_citiesFinds cities by name (in any of the six languages), country or region. Returns the city id that the other tools need.get_city_guideReturns one city: overview, headline sights, lesser-known sights, and every sight with category, coordinates and visit time. `detail: "full"` adds every long description.list_countriesLists the covered countries with their city ids.get_catalog_overviewReturns coverage totals, languages, and the exact values that the `categories`, `interests` and `periods` filters accept.recommend_attractionsPicks sights in one city for the traveler's interests, favourite periods, headline sights or hidden gems, indoor or outdoor, and time available. Each pick says why it was chosen.recommend_destinationsRanks cities for interests or historical periods, for example "best cities for Byzantine history", and says why.compare_citiesCompares two to four cities side by side: sights, days needed, strongest interests and periods, share of indoor sights, headline sights and the distance between them. Says which city is stronger for each interest or period.find_day_tripsLists covered cities that make a day trip from a base city, ranked by distance, interests and fame, with what to see there in one day. Sea crossings that need a flight are left out; short ferry trips are marked.plan_walking_tourBuilds an ordered walking route in one city for a time budget. Returns each stop with walking minutes, time on site, clock times, and a Google Maps walking link.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": {
"gingerguide-city-catalog-2": {
"command": "npx",
"args": [
"-y",
"gingerguide"
]
}
}
}