Skip to main content
Glama
AirTreks MCP

AirTreks MCP

by Airtreks

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.

Now with real 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.

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/mcp

Cursor

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

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

No API key is needed for any tool, the consultant handoff included. A key is optional and only raises your daily limit; append it to the URL if your client cannot send custom headers, as claude.ai connectors cannot:

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

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-mcp

Then ask your agent:

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

Related MCP server: wander-agent

One call, one answer: a 7-leg RTW

Your user wants six stops around the world. Google Flights gives up. One plan_route call lays the trip out, and one route_estimate call says what it costs. Neither one picks airlines: AirTreks consultants do that when they build the ticket.

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

Real plan_route response, trimmed for length (the full version has 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"],
  "customBuild": {
    "strategy": "7-leg route. 1 surface sector opportunity.",
    "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"
      }
    ],
    "complexity": "moderate"
  }
}

And route_estimate on the same cities:

{
  "cabin": "economy",
  "currency": "USD",
  "estimate": { "low": 1616.43, "high": 2465.75 },
  "confidence": "medium",
  "basis": "1,616-2,466 USD per person, from AirTreks fare history. We have history for most of this route, but not all of it."
}

That is a range from past AirTreks bookings, not a quote. For a real number, trip_idea_create hands the complete trip - route, a date for every leg, passengers, cabin and the traveler's answers to our planning questions - to an AirTreks consultant who prices and books it.

Tools

All tools are free and need no API key — 100 requests/day per IP.

Routing

Tool

Description

plan_route

Lay out a multi-city trip - direction, regions crossed, backtracking, surface-sector options, and how complex it is to ticket. No airline picks

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 a multi-city itinerary into legs with surface-sector options and how much each leg benefits from a consultant. No airline picks

Pricing

Tool

Description

route_estimate

Price range for a route from AirTreks fare history. No dates needed, answers in about a quarter of a second — the right tool when someone asks "what will this cost?" before anything is decided

fare_quote

Live fares for one specific itinerary on specific dates, priced as a single ticket

itinerary_quote

Prices a whole multi-stop trip and returns several ways to ticket it — cheapest, fastest, fewest stops — with the tickets each one is built from. Takes about a minute, so it returns a reference immediately

itinerary_quote_status

Fetches an itinerary_quote result by its reference, waiting up to about 40 seconds for one still pricing. Free to call again

Consultant handoff

Tool

Description

trip_idea_create

Hand off to an AirTreks human travel consultant - submits the trip request with the full routing analysis attached

Submits real customer contact details, so only call it with the customer's knowledge and consent. Repeat submissions of the same email + route inside 24 hours return the existing trip request rather than creating a duplicate.

Why this data is different

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

  • 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 - we know what airline combinations break ticketing and what to route instead

  • Proven routing templates from working with Multi-Stop and Around the World Intineraries for inviduals, families and large group

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 — every tool, trip_idea_create included

  • Registered: higher limits with an API key (X-API-Key header, or ?key= for clients that cannot set headers)

Endpoints

Path

Description

/mcp

MCP protocol endpoint (Streamable HTTP)

/api/{tool}

REST twin of each tool (POST, JSON body)

/openapi.json

OpenAPI 3.1 spec for the REST surface

/health

Health check

/register

Get an API key for a higher rate limit (POST)

/privacy

Privacy policy

/favicon.ico, /favicon.svg

AirTreks mark — the icon AI directories show for this server

/

Server info

License

AGPL-3.0-only

Available Tools

7 tools
custom_route_buildAInspect

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_matchAInspect

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.

hub_checkAInspect

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.

plan_routeAInspect

The primary entry point for any multi-city trip. Give it your cities — it automatically evaluates Star Alliance RTW, oneworld RTW, AND custom mixed-carrier builds, then recommends the best approach. Handles direction detection, backtracking analysis, alliance feasibility, surface sectors, and carrier selection. The customer doesn't need to know if their trip is alliance or custom — this tool figures it out.

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

route_suggestAInspect

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_validateAInspect

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_createAInspect

Create a trip idea in AirTreks APEX system — hands off to a human consultant. Automatically runs plan_route to include full routing analysis, carrier recommendations, and consultant value assessment in the lead. The consultant starts informed, not cold. Use this when the customer is ready to get a real quote.

Inputs: email (required), cities (required), name, cabin, +8 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'plan_route' and 'custom_route_build' both handle custom routing; descriptions clarify that 'plan_route' is the primary entry point while 'custom_route_build' is for complex cases.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., 'custom_route_build', 'fare_product_match', 'hub_check'). No mixed conventions or ambiguous names.

    Tool Count5/5

    Seven tools cover the core workflow of multi-city trip planning: planning, custom building, fare matching, hub checking, route suggestion, validation, and lead creation. This scope is well-balanced.

    Completeness4/5

    The tool set covers the main planning and validation needs, but lacks update/delete operations for trip ideas, which may require human follow-up. This is a minor gap given the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers