# SEKeener/airtreks-mcp [Health: Active]

**Category:** 🚆 Travel & Transportation  
**Repository:** https://github.com/SEKeener/airtreks-mcp  
**GitHub Stars:** 3  
**npm Downloads (last month):** 499  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sekeener-airtreks-mcp

## Description
Complex multi-city flight routing intelligence. 7 tools: plan round-the-world trips across 60+ carriers, validate Star Alliance and oneworld alliance routings, get segment-by-segment carrier recommendations, identify surface sector savings, and hand off to human consultants. No API key needed (100 req/day free). Remote endpoint: https://mcp.airtreks.com/mcp

## Tools
Capabilities this server exposes over MCP:

- **plan_route** — 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.
- **trip_idea_create** — Submit the customer's trip to AirTreks — a human travel consultant takes over from there. Automatically runs plan_route to attach the full routing analysis and carrier recommendations to the trip request, so the consultant starts informed, not cold. Use this when the customer is ready to get a real quote. Requires the customer's name, email, at least 2 cities (3-letter IATA codes), a departure date for every leg, and answers to AirTreks' planning questions — call once without questionsAnswers to receive the current questions to ask.
- **route_estimate** — 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.
- **fare_quote** — 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.
- **itinerary_quote** — 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 and you fetch the result with itinerary_quote_status. Keep that reference — it is the only way to retrieve the quote.
- **itinerary_quote_status** — Fetch the result of an itinerary_quote using the quoteReference it returned. Returns status 'pending' with how long to wait, or the finished options. Costs nothing and does no searching, so poll it rather than starting a second quote.
- **route_validate** — 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.
- **route_suggest** — 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.
- **hub_check** — 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.
- **fare_product_match** — 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.
- **custom_route_build** — 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.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "airtreks-mcp": {
    "command": "npx",
    "args": ["-y","airtreks-mcp"]
  }
}
```

## Documentation

## What SEKeener/airtreks-mcp MCP server does

SEKeener/airtreks-mcp MCP server gives agents tools for planning and pricing itineraries that exceed the scope of a simple one-way or round-trip search. It works with multi-city, round-the-world, open-jaw, and mixed-carrier journeys, using routing information based on AirTreks fare-construction data.

The main entry point is `plan_route`. Given a sequence of three-letter airport or city codes, it compares Star Alliance, oneworld, and custom routing approaches. The response can include travel direction, backtracking, alliance feasibility, carrier recommendations, surface-sector opportunities, and an overall recommendation.

Additional routing tools validate an itinerary, suggest templates, inspect connections between airports, select a fare-product type, or divide a complex trip into separately ticketable segments. Pricing tools distinguish between historical estimates, live fares for one itinerary, and asynchronous pricing across several tickets.

## How it works

The remote MCP endpoint is `https://mcp.airtreks.com/mcp` and uses Streamable HTTP. Agents send tool calls with route details such as city codes, dates, budget information, or alliance preferences, depending on the tool. `route_estimate` needs no dates and returns a historical per-person USD range rather than current availability. `fare_quote` requires dates for every flown leg and prices one itinerary as a single fare.

For trips that may require multiple tickets, `itinerary_quote` returns a `quoteReference` immediately. `itinerary_quote_status` uses that reference to check whether the result is still pending or has finished. The REST equivalents are available under `/api/{tool}`, with an OpenAPI description at `/openapi.json`.

SEKeener/airtreks-mcp MCP server also supports a consultant handoff through `trip_idea_create`. That tool submits the route and customer information to AirTreks after collecting the required details. It runs route planning first so the request includes the routing analysis. Use it only with the customer’s knowledge and consent.

## Setup and configuration

Connect an MCP client to the remote URL, or run the local package with:

```bash
npx airtreks-mcp
```

Claude Desktop can add the endpoint as a custom connector. Claude Code can register it with the HTTP transport, and Cursor can place the URL in `.cursor/mcp.json`. Other MCP clients can use the same Streamable HTTP configuration or the local stdio command.

No API key is needed for the free tier, which allows 100 requests per day per IP. A registered key raises the limit and can be supplied through an `X-API-Key` header or as a `key` URL parameter when a client cannot send custom headers. There are no required environment variables documented for the server.

## Tools and capabilities

- `plan_route`: Compare alliance and custom approaches for a multi-city route.
- `route_validate`: Check alliance rules, dead legs, carrier issues, and bookability.
- `route_suggest`: Return up to three routing templates based on regions and preferences.
- `hub_check`: Find connection options and possible hub fixes between airports.
- `fare_product_match`: Recommend RTW, Circle Pacific, Circle Atlantic, Open Jaw, or custom multi-city pricing structures.
- `custom_route_build`: Split difficult routes into ticketable segments with carrier suggestions.
- `route_estimate`, `fare_quote`, and `itinerary_quote`: Provide historical ranges, live single-fare pricing, or multi-ticket quote options.
- `itinerary_quote_status`: Retrieve an asynchronous itinerary quote.
- `trip_idea_create`: Submit a prepared trip to an AirTreks consultant.

## Limitations and notes

Historical estimates are not live quotes and do not account for current availability or seasonality. A single-fare quote may be unpriceable for long or unusual multi-continent routes; those trips may need separate tickets. `itinerary_quote` can take about a minute and should be polled with its returned reference rather than submitted repeatedly. Repeated consultant submissions for the same email and route within 24 hours return the existing request.

_Full upstream README: https://allmcps.com/mcp/sekeener-airtreks-mcp/readme_