AirLabs MCP Server
OfficialRelated Servers
Alternatives to AirLabs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to query flight routes, real-time flight tracking, weather, and transfer flights via standardized MCP tools.10MIT

FlightQueueofficial
AlicenseNot gradedqualityBmaintenanceProvides AI assistants with real-time and forecast airport intelligence, including security wait times, FAA delays, EU border queues, lounge and terminal info, aviation weather, and baggage performance for over 8,000 airports.MIT- AlicenseAqualityCmaintenanceProvides real-time and historical flight data via the Flightradar24 API, enabling AI assistants to track aircraft positions, flight summaries, and airport details.15205 npm29MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural-language and tool-based access to live flight status, airport departure/arrival boards, and scheduled flight timetables via the Cirium FlightStats Flex API.252 npmMIT

FlightClawofficial
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, price-track, and book flights across ~300 airlines, with traveler profiles, preferences, and email fare-drop alerts.75MIT- FlicenseCqualityCmaintenanceEnables AI assistants to search for flights, book them, check booking status, and cancel bookings using mock flight data with no API keys required.4-
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: airport code search, live schedules, airline info, aircraft lookup, delay monitoring, route timetables, etc. Descriptions preemptively clarify overlaps (e.g., get_airport_schedule vs. find_routes vs. monitor_delays), ensuring agents can reliably select the correct tool.
Tool names mix patterns: get_ prefixed info tools (get_airline_info), find_ verbs (find_routes), lookup_, monitor_, search_, track_. While all are descriptive, the lack of a single consistent convention (e.g., verb_noun) adds slight ambiguity, especially between get_airport_schedule and get_flight_status.
With 12 tools, the set is well-scoped for an aviation data server. Each tool addresses a distinct core function (resolving codes, live flight data, aircraft details, delays, routes) without redundancy or bloat. The count feels appropriate for the domain's complexity.
The tool set covers a comprehensive range of aviation information needs: airport/airline details, code resolution, live schedules, route planning, delay monitoring, flight status, aircraft lookup, and live tracking. No obvious gaps exist—the surface enables agents to answer most common queries about flights, airports, airlines, and aircraft.