FlightByte MCP Server
OfficialRelated Servers
Alternatives to FlightByte 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
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to ask what aircraft are flying near a location, track a specific flight's live position, route, aircraft details and photo, and surface emergency-squawking or military aircraft. It exposes four tools (flights_near, track_flight, emergencies, military_aircraft) backed by merged volunteer ADS-B networks and a global snapshot.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients such as Claude, Cursor, VS Code, and Windsurf to read and manage workspaces, projects, tasks, and AI agents, and to build automations through natural language. It also includes an OpenAPI codegen that turns any OpenAPI spec into MCP tools.1,958 npmMIT

AirLabs MCP Serverofficial
AlicenseAqualityDmaintenanceProvides AI assistants with access to real-time flight data, airport schedules, delays, and aviation reference databases through natural language queries.12182 npmMIT- AlicenseNot gradedqualityDmaintenanceProvides comprehensive flight tracking capabilities using the OpenSky Network API, enabling real-time flight data, geographic searches, historical data, and airport operations through MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants such as Claude Desktop and Cursor to access live satellite orbit propagation, ground-station pass prediction, geodetic conversion, and Doppler shift calculations through MCP tools.1MIT
TDQS
Scored across 15 tools
The subscription tools (get/list/update/pause/resume/delete) are cleanly separated, but get_flight and search_flights are explicitly the same lookup with the same payload, differing only in HTTP method, and get_flight_timeline duplicates the `timeline` already embedded in get_flight. The descriptions do call out these overlaps ('use either one, not both', 'call this only when the history alone is needed'), which mitigates but does not remove the misselection risk.
Every tool is snake_case with a verb-first pattern: search_docs, get_doc_page, get_flight, search_flights, get_flight_timeline, create/list/get/update/pause/resume/delete_subscription, send_test_event, list_deliveries, list_events. Resource nouns are consistent (_subscription, _deliveries) and no conventions are mixed.
15 tools is at the top of the well-scoped range and the surface maps cleanly onto four areas: docs, flight lookup, subscription lifecycle, and webhook observability. One tool is arguably redundant (search_flights vs get_flight), which keeps it just short of ideal.
Subscription lifecycle is fully covered (create/list/get/update/pause/resume/delete plus test event, deliveries and events for debugging), and docs plus flight lookup are covered. Minor gaps: no way to look up an airport/airline/route or search flights by route, so agents must rely on flight-number lookups or docs for that context.