Skip to main content
Glama

Server Details

Plan multi-city and RTW trips, estimate prices, and send complete trip requests to AirTreks.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Airtreks/airtreks-mcp
GitHub Stars
3
Server Listing
AirTreks MCP
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 11 tools

Disambiguation3/5

The descriptions work hard to separate fare_quote from route_estimate and itinerary_quote, and that trio is reasonably clear after reading. But plan_route, route_suggest, route_validate, custom_route_build, and fare_product_match all concern routing feasibility/recommendation and their boundaries only emerge from long prose caveats rather than naturally distinct scopes. An agent must cross-reference several descriptions before choosing, and misselection between route_validate and plan_route or route_suggest and custom_route_build is easy.

Naming Consistency3/5

All names are snake_case, which keeps things readable, but the word order varies: plan_route, route_estimate, route_suggest, fare_quote, and hub_check lead with a verb, while custom_route_build, fare_product_match, route_validate, and trip_idea_create put the verb last. The noun vocabulary also churns between 'route', 'trip', 'itinerary', and 'fare' for overlapping concepts. It is consistent in casing but not in pattern.

Tool Count4/5

Eleven tools is a healthy size for a multi-city trip-planning workflow, and the async pair itinerary_quote plus itinerary_quote_status earns its keep. There is mild redundancy in the routing-assistance cluster, but nothing is clearly filler. Count is not the problem here; overlap is.

Completeness4/5

The lifecycle is well covered: suggest, validate, plan, build, estimate, quote, and hand off to a human consultant, with an async status tool for the long-running quote. Gaps are minor but real — no city/airport or IATA-code lookup, no way to retrieve or amend a previously submitted trip_idea, and no re-fetch mechanism if the quoteReference is lost. Agents can work around these.

Available Tools

11 tools
custom_route_buildBuild a Custom Segmented RouteA
Read-only
Inspect

Break a complex multi-city itinerary into individually-ticketable segments with carrier recommendations. Handles routes that don't fit alliance fare rules — mixed carriers, LCCs, Gulf bridge connections, surface sectors. This is how AirTreks consultants build 90% of itineraries. Use this for any route with 4+ stops, backtracking, or region combinations that alliance fares can't cover.

Inputs: cities (required), pax, budget, preferences.

fare_product_matchMatch the Right Fare ProductA
Read-only
Inspect

Recommend the best fare product type for a route — RTW, Circle Pacific, Circle Atlantic, Open Jaw, or Custom Multi-City. Considers stop count, direction, and backtracking to match the right alliance fare structure.

Inputs: cities (required), isOneDirection, includeBacktracking.

fare_quotePrice a Specific Itinerary with Live FaresA
Read-only
Inspect

Get live, bookable-quality fares for one specific itinerary — actual flights, actual prices, for the dates given. Needs a departure date for every flown leg. Use this once the customer has settled on cities and dates and wants real numbers rather than a ballpark; use route_estimate instead when dates are still open. It prices the itinerary as a single fare, so very long or awkward multi-continent trips may come back unpriceable — those genuinely need to be split across separate tickets, which is what AirTreks consultants do by hand.

Inputs: dates (required), cities (required), cabin, adults, +3 more.

hub_checkCheck Airport Hub ConnectionsA
Read-only
Inspect

Check the best connection between two airports. Identifies dead legs (routes that fail on alliance fares), suggests hub routing fixes, and shows proven carrier combinations. Essential for transpacific, kangaroo, and intra-Asia routing.

Inputs: to (required), from (required), alliance.

itinerary_quotePrice a Whole Multi-Stop TripAInspect

Price a complete multi-stop or round-the-world trip and get back several ways of ticketing it — cheapest, fastest, fewest stops — with the actual tickets each one is built from. Use this for trips that will not go on a single fare, which is most itineraries with 3+ stops; use fare_quote when you want one specific itinerary on one ticket. It takes about a minute, so it returns a quoteReference immediately; call itinerary_quote_status with it straight away, and that call waits for the result. Keep that reference — it is the only way to retrieve the quote.

Inputs: dates (required), cities (required), cabin, adults, +2 more.

itinerary_quote_statusRetrieve a Multi-Stop Trip QuoteA
Read-only
Inspect

Fetch the result of an itinerary_quote using the quoteReference it returned. Call it straight away: it waits up to about 40 seconds for a quote that is still pricing, then returns the finished options, or status 'pending' if the quote needs one more call. Costs nothing and does no searching, so call it again rather than starting a second quote.

Inputs: quoteReference (required).

plan_routePlan a Multi-City RouteA
Read-only
Inspect

Lay out a multi-city trip: direction of travel, regions crossed, backtracking, where a surface sector could replace a flight, and how complex the trip is to ticket. Give it your cities. It does not choose airlines and gives no prices - use route_estimate for a price range and trip_idea_create to hand the trip to AirTreks.

Inputs: cities (required), pax, budget, preferences.

route_estimateEstimate the Price of a Multi-City RouteA
Read-only
Inspect

Get a price range for a multi-city or round-the-world trip, drawn from what AirTreks customers have actually paid on those routes. Give it the cities and it returns a per-person range in USD with how much history sits behind it. Use it when someone asks what a trip will cost and you don't have exact dates yet — it needs no dates and no passenger details. It is a range from past bookings, not a live quote, so it will not reflect today's availability or seasonality; it tells you the right ballpark before anyone commits to dates.

Inputs: cities (required), cabin.

route_suggestSuggest Multi-Stop RoutingsA
Read-only
Inspect

Get suggested multi-stop flight routings based on regions, direction, and alliance preference. Returns up to 3 proven routing templates with bookability ratings. Great for trip planning inspiration.

Inputs: regions (required), alliance, maxStops, tripType, +1 more.

route_validateValidate a Multi-City RoutingA
Read-only
Inspect

Validate a multi-city flight routing for feasibility. Checks alliance carrier rules, identifies dead legs, warns about poison carriers, and estimates bookability. Use this before building an itinerary to catch routing problems early.

Inputs: cities (required), alliance, carriers.

trip_idea_createSubmit a Trip Request (Consultant Handoff)A
Destructive
Inspect

Submit the customer's trip to AirTreks as a complete, structured trip request - a human travel consultant takes over from there. Ask the traveler for everything before calling, never guess or fill in defaults: name, email, the cities in order (3-letter IATA codes), a departure date for every leg, number of passengers, cabin (economy, premium or business), and their answers to AirTreks' planning questions. Also ask about budget, flexible dates, preferences and anything else the consultant should know. Call once without questionsAnswers to receive the current planning questions to put to the traveler.

Inputs: name (required), cabin (required), dates (required), email (required), +11 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.