A
licenseNot graded
qualityD
maintenanceWraps the official Flightradar24 MCP Server to expose it over HTTP/SSE for remote access, enabling MCP-compatible clients to query flight tracking data with client-provided API keys.
Apache 2.0
flightradar24-mcp-server
by Cyreslab-AI
Related Servers
Alternatives to flightradar24-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for FlightAware AeroAPI that enables live flight tracking, airport boards, operator and aircraft lookup, schedule retrieval, and flight alert management via natural language.34800 npm1MIT
- FlicenseAqualityCmaintenanceAn MCP server for live flight tracking and real-time status checks, including airport and airline code resolution, powered by the free AviationStack API.4-
- MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Travelpayouts (Aviasales) API. It provides 13 tools for flight search, price calendars, hotel search, and airport/airline/city lookup.59 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for fetching METAR and TAF aviation weather data for airports by ICAO code.21 PyPIMIT
TDQS
A4/5.0
Scored across 8 tools
Disambiguation4/5
Most tools clearly target distinct resources: airports, airlines, tracks, live positions, and historical summaries. The only mild overlap is between search_flights and get_flights_in_zone, both returning currently airborne flights, but their filter-based vs bounding-box approaches are described clearly enough to avoid significant confusion.
Naming Consistency4/5
The naming follows a mostly consistent get_X pattern (get_flight_data, get_airport_data, get_flight_summary). Minor deviations include search_flights using a different verb and the singular/plural variation between get_flight_tracks and get_flights_in_zone, but the overall convention remains predictable.
Tool Count5/5
Eight tools is well-scoped for a flight tracking and aviation data server. Each tool covers a meaningful query type without unnecessary redundancy, and the count fits comfortably within the ideal range.
Completeness4/5
The core workflows are covered: live flight search, live flight detail, historical summaries, detailed tracks, airport lookup, airline lookup, and API usage. Minor gaps such as airport arrival/departure boards or aircraft-specific data are absent, but common FR24 use cases are fully workable.
Maintenance
ActivityMaintained
ResponsivenessNo issues