AirTreks is an MCP server with 11 tools an agent can call, among them custom_route_build, fare_product_match, fare_quote. It answers at https://mcp.airtreks.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Multi-city flight routing intelligence — plan RTW trips, validate alliances, get carrier picks.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 AirTrek Inputs: cities, budget, preferences, pax |
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. Inputs: cities, isOneDirection, includeBacktracking |
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 Inputs: cities, dates, adults, children, infants, cabin |
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. Inputs: from, to, alliance |
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 Inputs: cities, dates, adults, children, infants, cabin |
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. Inputs: quoteReference |
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 Inputs: cities, budget, preferences, pax |
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 Inputs: cities, cabin |
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. Inputs: regions, direction, alliance, maxStops, tripType |
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. Inputs: cities, carriers, alliance |
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, Inputs: email, name, phone, cities, dates, passengers |
Every block below points at https://mcp.airtreks.com/mcp. Pick your client and copy.
claude mcp add --transport http airtreks https://mcp.airtreks.com/mcp
{
"mcpServers": {
"airtreks": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.airtreks.com/mcp"]
}
}
}{
"mcpServers": {
"airtreks": {
"url": "https://mcp.airtreks.com/mcp"
}
}
}{
"servers": {
"airtreks": {
"type": "http",
"url": "https://mcp.airtreks.com/mcp"
}
}
}{
"context_servers": {
"airtreks": {
"url": "https://mcp.airtreks.com/mcp"
}
}
}{
"mcpServers": {
"airtreks": {
"serverUrl": "https://mcp.airtreks.com/mcp"
}
}
}{
"mcpServers": {
"airtreks": {
"url": "https://mcp.airtreks.com/mcp"
}
}
}name: AirTreks
version: 0.0.1
schema: v1
mcpServers:
- name: AirTreks
type: streamable-http
url: https://mcp.airtreks.com/mcp{
"mcpServers": {
"airtreks": {
"httpUrl": "https://mcp.airtreks.com/mcp"
}
}
}{
"mcpServers": {
"airtreks": {
"type": "http",
"url": "https://mcp.airtreks.com/mcp"
}
}
}{
"mcpServers": {
"airtreks": {
"url": "https://mcp.airtreks.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.airtreks.com%2Fmcp&type=streamable_http&id=airtreks&name=AirTreks
It answered our last check on 19 October 2026 in 282 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
11, as returned by the server's own tools/list on 12 September 2026: custom_route_build, fare_product_match, fare_quote, hub_check, itinerary_quote, itinerary_quote_status, plan_route, route_estimate, and 3 more.
It answered our last check on 19 October 2026 in 282 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.airtreks.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.airtreks. Endpoint host: mcp.airtreks.com. ARD identifier: urn:air:io.github.airtreks:mcp:airtreks-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.