Airtreks MCP Server

Multi-city flight routing intelligence — plan RTW trips, validate alliances, get carrier picks. The airtreks mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 9 defined tools rather than through you.

What it actually does

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

• 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

Its toolset

Everything the assistant can do here goes through one of these:

• plan_route — Primary entry point - give it cities, it evaluates Star Alliance RTW, oneworld RTW, and custom mixed-carrier builds, then recommends the best approach
• route_validate — Validate a multi-city routing - alliance rules, dead legs, poison carriers, bookability
• route_suggest — Get 3 suggested routings by region, direction, and alliance
• hub_check — Best connection between two airports - dead leg detection + hub fixes
• fare_product_match — Match the right fare product (RTW, Circle Pacific/Atlantic, Open Jaw, Custom) with typical price ranges
• custom_route_build — Break complex itineraries into individually-ticketable segments with carrier recommendations
• trip_idea_create — Hand off to an AirTreks human consultant - creates a trip idea in APEX with the full routing analysis attached
• Cursor — Add to .cursor/mcp.json (or Cursor Settings → MCP → Add new server):
• ChatGPT — Settings → Apps & Connectors → enable Developer mode (Pro/Business plans) → add https://mcp.airtreks.com/mcp as a custom connector

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Airtreks's toolset — plan_route, route_validate, route_suggest and 6 more — is a fair guide to whether it matches your workflow. It is maintained by SEKeener; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Airtreks's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Airtreks.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the airtreks mcp server does with a few real requests.