Summary
One key, and the whole flight-tracking question set becomes answerable in the conversation.
The tools split into live data and reference data, and the reference ones exist so the live ones work: search_airport_code turns the names a person uses into the codes the API needs, then the flight, schedule and delay calls run against them. Everything reads AirLabs, so nothing here books, changes or cancels anything.
What it is
A single-file server over the AirLabs aviation API: live flight status, airport boards, delays, aircraft positions and the reference databases behind them.
What you get
- Status, gate, terminal and delay for one flight by its IATA or ICAO number (get_flight_status)
- A departures or arrivals board for any airport (get_airport_schedule), and flights delayed beyond a threshold you set (monitor_delays)
- Live aircraft positions with coordinates, altitude, speed and heading, by area, airline or registration (track_live_flights)
- Which airlines fly a route and whether a nonstop exists (find_routes)
- Reference lookups for airlines, airports and aircraft by tail number, plus the closest airport to a coordinate (get_airline_info, get_airport_info, lookup_aircraft, find_nearest_airport)
- Name-to-code resolution, so a city or country name becomes the code the other calls need (search_airport_code, get_city_info, get_country_info)
Requirements
A current Node.js and an AirLabs API key, free on signup, passed as AIRLABS_API_KEY. Installed globally from npm or run with npx.
Setup effort
One command plus a key — npm install -g @airlabs-co/airlabs-mcp, then supply credentials