AirTreks MCP
The AirTreks MCP server is a specialized tool for planning and analyzing complex multi-stop flight itineraries (round-the-world, open-jaw, surface segments) that standard flight search engines can't handle. It uses real AirTreks fare-construction data, routing templates, and bookability analytics.
Core capabilities:
Plan complex routes (
plan_route) — The primary entry point: provide an ordered list of city/airport codes and get a comprehensive analysis that evaluates Star Alliance RTW, oneworld RTW, and custom mixed-carrier builds, with confidence ratings, carrier suggestions, and bookability estimates.Validate routings (
route_validate) — Check multi-city routings against alliance carrier rules, identify known "dead legs," warn about poison carrier combinations, and get a bookability estimate.Get route suggestions (
route_suggest) — Discover up to 3 proven routing templates based on regions, travel direction (eastbound/westbound), alliance preference, max stops, and trip type.Check hub connections (
hub_check) — Find the best connections between two airports, detect dead legs, and get hub routing fixes and proven carrier combinations.Match fare products (
fare_product_match) — Determine the most suitable fare product (RTW, Circle Pacific, Circle Atlantic, Open Jaw, Custom Multi-City) with typical price ranges.Build custom routes (
custom_route_build) — Break complex itineraries into individually-ticketable segments with carrier recommendations, handling mixed carriers, LCCs, Gulf bridge connections, and surface sectors.Hand off to a human consultant (
trip_idea_create, API key required) — Send a fully analyzed trip to an AirTreks human consultant for real pricing and booking, with routing analysis attached automatically.
Key data behind the tools:
53 known dead legs from 1,400+ real fare-construction failures
Measured bookability rates by leg count (91% at 3–4 legs, 61% at 5–6, 6% at 7+)
60+ carrier database with poison-carrier and hub-fix data
20 proven routing templates from actual AirTreks bookings
Access: Free tier allows 100 requests/day with no API key. A registered tier with higher limits is available via an X-API-Key header (register at POST https://mcp.airtreks.com/register).
AirTreks MCP Server
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.
30-second setup
Claude Desktop
Settings → Connectors → Add custom connector → paste https://mcp.airtreks.com/mcp.
Claude Code
claude mcp add --transport http airtreks https://mcp.airtreks.com/mcpCursor
Add to .cursor/mcp.json (or Cursor Settings → MCP → Add new server):
{
"mcpServers": {
"airtreks": {
"url": "https://mcp.airtreks.com/mcp"
}
}
}ChatGPT
Settings → Apps & Connectors → enable Developer mode (Pro/Business plans) → add https://mcp.airtreks.com/mcp as a custom connector.
Any other MCP client
Same JSON shape as Cursor above (Streamable HTTP). Prefer stdio? Run it locally:
npx airtreks-mcpThen ask your agent:
Plan a round-the-world trip: San Francisco, Tokyo, Bangkok, Singapore, Delhi, Istanbul, London, back to San Francisco.
Related MCP server: Award Flight Daily MCP Server
One call, one answer: a 6-stop RTW
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. One plan_route call 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_create hands 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.
Tools
Free (no API key, 100 req/day)
Tool | Description |
| Primary entry point - give it cities, it evaluates Star Alliance RTW, oneworld RTW, and custom mixed-carrier builds, then recommends the best approach |
| Validate a multi-city routing - alliance rules, dead legs, poison carriers, bookability |
| Get 3 suggested routings by region, direction, and alliance |
| Best connection between two airports - dead leg detection + hub fixes |
| Match the right fare product (RTW, Circle Pacific/Atlantic, Open Jaw, Custom) with typical price ranges |
| Break complex itineraries into individually-ticketable segments with carrier recommendations |
API key required
Tool | Description |
| Hand off to an AirTreks human consultant - creates a trip idea in APEX with the full routing analysis attached |
Get a key: POST https://mcp.airtreks.com/register with {"email": "you@example.com"}
Why this data is different
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 templates from top AirTreks bookings
No other flight tool returns this because no other flight tool has priced these failures.
REST API (no MCP client required)
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
Rate limits
Free: 100 requests/day per IP, no key needed
Registered: higher limits with an API key (
X-API-Keyheader)trip_idea_createrequires a key
Endpoints
Path | Description |
| MCP protocol endpoint (Streamable HTTP) |
| REST twin of each tool (POST, JSON body) |
| OpenAPI 3.1 spec for the REST surface |
| Health check |
| Get an API key (POST) |
| Privacy policy |
| Server info |
License
AGPL-3.0-only
Maintenance
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SEKeener/airtreks-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server