Aviationstack MCP Server
Related Servers
Alternatives to Aviationstack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAviationstack MCP server that provides tools to access global flight and aviation data including airports, airlines, cities, countries, and routes.145 npmMIT
- 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-
- AlicenseCqualityCmaintenanceA Model Context Protocol (MCP) server that provides real-time flight tracking and status information using the AviationStack API.35,022 npm7MIT
- 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.34722 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides flight search capabilities using the Aviasales API, allowing users to search, filter, and get details on flights and generate booking links.4GPL 3.0
- AlicenseAqualityCmaintenanceMCP server giving AI agents access to real-time aviation data — live flight tracking, airport weather, airline and airport information.103MIT
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes, especially the time-scoped flight tools (today, future, past) and the reference list tools. The two random aircraft tools could be confused at a glance, but their descriptions clearly separate aircraft types from individual airplanes.
The tool names mostly follow consistent snake_case patterns: get_ for single lookups, list_ for catalog pages, and random_ for sampling tools. A few names like flights_with_airline and flight_arrival_departure_schedule deviate from the verb_noun pattern, but the overall convention remains readable and predictable.
Thirteen tools is a well-scoped size for a flight data API covering flight status, schedules, and reference data. Each tool has a defined role, and the count is neither bloated nor too thin.
The server covers the core flight workflows well: specific flight status, airline flight lists, today's/future/historical schedules, and route/reference lookups. Minor gaps exist, such as no specific lookup for random catalog entities beyond sampling, but agents can complete most flight-status tasks without dead ends.