Airtreks Mcp

- Plan complex multi-stop routes— Ask for a round-the-world or open-jaw itinerary andplan_routeevaluates alliance RTW fares vs. custom mixed-carrier builds, returning a recommended approach with per-leg carrier picks.
- Validate routing feasibility— Useroute_validateto check a multi-city itinerary against alliance rules, dead legs, poison carriers, and bookability rates before committing to tickets.
- Get pricing ranges instantly— Ask "what will this cost?" androute_estimatereturns a historical price range for any route in under a second, no dates needed.
- Compare ticketing strategies—itinerary_quoteprices a full multi-stop trip several ways (cheapest, fastest, fewest stops) and shows the tickets each option is built from.
- Find better connections—hub_checkidentifies the best hub between two airports, flagging dead legs and suggesting fixes that actually ticket successfully.
- Hand off to a human expert—trip_idea_createsubmits the full routing analysis to an AirTreks consultant for expert pricing and booking.

The complex-itinerary tool for AI agents.Multi-stop, round-the-world, open-jaw, surface segments - the trips that standard flight search can't handle. When your user asks for 3+ stops across continents, this server answers with routing analysis built on real AirTreks fare-construction data: 60+ carriers, 53 known dead legs, bookability rates measured from 1,400+ real fare attempts, and 20 proven routing templates from actual bookings.

Live endpoint:https://mcp.airtreks.com/mcp- free, no API key, 100 requests/day.

Now withreal prices: a historical range for any route in under a second, live fares for a specific itinerary, and a full multi-stop trip priced across several tickets — the same trip can vary three-fold depending on how it is ticketed, and that is the part no other flight tool will tell you.

Settings → Connectors →Add custom connector→ pastehttps://mcp.airtreks.com/mcp.

claude mcp add --transport http airtreks https://mcp.airtreks.com/mcp

Add to.cursor/mcp.json(or Cursor Settings → MCP → Add new server):

{ "mcpServers": { "airtreks": { "url": "https://mcp.airtreks.com/mcp" } } }

To use the consultant handoff (trip_idea_create), append your API key to the URL — hosted clients such as claude.ai connectors cannot send custom headers:

https://mcp.airtreks.com/mcp?key=at_your_key

Settings →Apps & Connectors→ enable Developer mode (Pro/Business plans) → addhttps://mcp.airtreks.com/mcpas a custom connector.

Same JSON shape as Cursor above (Streamable HTTP). Prefer stdio? Run it locally:

Plan a round-the-world trip: San Francisco, Tokyo, Bangkok, Singapore, Delhi, Istanbul, London, back to San Francisco.

Your user wants six stops around the world. Google Flights gives up. Alliance RTW booking sites will let them build it, then fail at ticketing. Oneplan_routecall tells your agent what actually works:

{ "cities": ["SFO", "NRT", "BKK", "SIN", "DEL", "IST", "LHR", "SFO"], "budget": "mid" }

Real response, trimmed for length (the full version includes carrier alternatives and consultant notes for all 7 legs):

{ "route": "SFO -> NRT -> BKK -> SIN -> DEL -> IST -> LHR -> SFO", "totalLegs": 7, "isRoundTrip": true, "direction": "westbound", "backtracking": false, "regionsCrossed": ["americas", "asia", "europe"], "recommended": { "approach": "custom", "confidence": "high", "reason": "7 legs — alliance fares have <6% bookability. Custom build with mixed carriers is the way to go." }, "customBuild": { "strategy": "Mixed-carrier build using alliance carriers, Gulf bridge connections. 1 surface sector opportunity.", "segments": [ { "leg": 1, "from": "SFO", "to": "NRT", "carrier": { "code": "NH", "name": "ANA", "why": "Best transpacific availability. LAX/SFO/SEA-NRT direct." } }, { "leg": 5, "from": "DEL", "to": "IST", "carrier": { "code": "TK", "name": "Turkish Airlines", "type": "gulf-bridge", "why": "Cheapest Asia-Europe usually. IST connects everywhere." } } ], "surfaceSectors": [ { "insteadOf": "BKK -> SIN (leg 3)", "suggestion": "Bangkok to Singapore through Malaysia. Train, bus, or ultra-cheap LCC. Adds Malaysia and possibly Penang, KL, Melaka.", "savings": "Saves $100-250" } ] }, "allianceFeasibility": { "starAlliance": { "viable": false, "summary": "Technically possible on Star Alliance but only 6% bookability at 7 legs. Custom build strongly recommended." }, "oneworld": { "viable": false, "summary": "Technically possible on oneworld but only 6% bookability at 7 legs. Custom build strongly recommended." } } }

That single call just told your agent four things it can't get anywhere else:

- Alliance RTW fares fail on this trip.7 legs prices at 6% bookability - your user would build it, hit a wall at ticketing, and blame you.
- The build that works:a per-leg carrier plan - ANA transpacific, Turkish Airlines as the Asia-Europe bridge, each with alternatives and trade-offs.
- Where to not fly at all:Bangkok to Singapore is cheaper overland through Malaysia, saving $100-250 and adding a country.
- What it typically costs:fare_product_matchputs this trip at $2,500-$8,000 economy on an alliance RTW fare, typically $3,000-$12,000 as a custom build.

Those are honest ranges, not quotes - exact pricing on a 7-leg mixed-carrier itinerary depends on fare-class availability the day you book. For a real number,trip_idea_createhands the full routing analysis to an AirTreks consultant who prices and books the actual ticket. Your user gets an expert who starts informed, not a form to fill out.

Get a key:POST https://mcp.airtreks.com/registerwith{"email": "[email protected]"}

AirTreks has built complex multi-stop itineraries since 1987. This server exposes what that history taught us:

- 53 dead legs- city pairs that look bookable but fail on alliance fares, learned from 1,400+ real fare-construction failures
- Bookability rates by leg count- measured, not estimated (91% at 3-4 legs, 61% at 5-6, 6% at 7+)
- Poison carriers and hub fixes- which airline combinations break ticketing and what to route instead
- 20 proven routing templatesfrom top AirTreks bookings

No other flight tool returns this because no other flight tool has priced these failures.

Every tool is also a plain REST endpoint - same tools, same rate limits, JSON in/out. For agent frameworks that consume REST instead of MCP:

curl -X POST https://mcp.airtreks.com/api/plan_route \ -H "Content-Type: application/json" \ -d '{"cities": ["LAX", "NRT", "BKK", "LHR", "LAX"]}'

Full OpenAPI 3.1 spec:https://mcp.airtreks.com/openapi.json

RAG Search over your content powered by Inkeep