air-routes.com
Global scheduled passenger flight routes: which exist, direct or connecting, and days flown.
Should I use this
Quality & Safety
Findings (2)
- LOWTool 'resolve_airport' description lacks action verbin resolve_airport
- LOWTool 'route_detail' description lacks action verbin route_detail
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"air-routes": {
"url": "https://air-routes.com/mcp"
}
}
}Remote endpoints
https://air-routes.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟢find_connections(from_airport, to_airport, max_stops, max_flying_min, include_charter)
Find flight connections between two airports (airport codes). Returns the fewest-stops tier that has any option: direct if available, else one-stop, else two-stop (up to max_stops), never a mix. Options sort by flying time; layover tiers cap at 7. Charter flights (tour-operator capacity, not bookable seat-only with the airline) are excluded unless include_charter=true, and never appear inside multi-leg itineraries. Data: scheduled passenger routes operating now, with seasonality labels — not fares, not booking, not date-specific schedules.
Input Schema
{
"type": "object",
"properties": {
"from_airport": {
"title": "From Airport",
"type": "string"
},
"to_airport": {
"title": "To Airport",
"type": "string"
},
"max_stops": {
"default": 2,
"title": "Max Stops",
"type": "integer"
},
"max_flying_min": {
"default": 1440,
"title": "Max Flying Min",
"type": "integer"
},
"include_charter": {
"default": false,
"title": "Include Charter",
"type": "boolean"
}
},
"required": [
"from_airport",
"to_airport"
],
"title": "find_connectionsArguments"
}🟢airport_destinations(airport, include_charter)
List every direct flight from an airport (airport code), with full schedule detail per destination: airlines, schedule (day + times), flying_min, seasonality, booking URL. Prefer this over N× route_detail when planning from one hub. Data: scheduled passenger routes operating now, with seasonality labels — not fares, not booking, not date-specific schedules.
Input Schema
{
"type": "object",
"properties": {
"airport": {
"title": "Airport",
"type": "string"
},
"include_charter": {
"default": false,
"title": "Include Charter",
"type": "boolean"
}
},
"required": [
"airport"
],
"title": "airport_destinationsArguments"
}⚪resolve_airport(query)
Resolve a free-text city or airport name to airport codes (e.g. 'london' → LHR, LGW, STN, LTN, LCY). Use before other tools when the user gives city names. airport_code is the 3-letter IATA airport code.
Input Schema
{
"type": "object",
"properties": {
"query": {
"title": "Query",
"type": "string"
}
},
"required": [
"query"
],
"title": "resolve_airportArguments"
}⚪route_detail(route_id, include_charter)
Detail for one route (e.g. 'OTP-BCN'): airlines, schedule and seasonality. Data: scheduled passenger routes operating now, with seasonality labels — not fares, not booking, not date-specific schedules.
Input Schema
{
"type": "object",
"properties": {
"route_id": {
"title": "Route Id",
"type": "string"
},
"include_charter": {
"default": false,
"title": "Include Charter",
"type": "boolean"
}
},
"required": [
"route_id"
],
"title": "route_detailArguments"
}Community
Evidence