Aviationstack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AVIATION_STACK_API_KEY | Yes | Your Aviationstack API key (a free key is available from https://aviationstack.com/signup/free). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use these tools to fetch real-time, historical, and reference aviation data from Aviationstack. To look up one specific flight, use get_flight_status with its IATA number. Provide IATA/ICAO codes when available and request small limits first. Every tool returns {'ok': true, 'count': N, 'data': [...]} or {'ok': false, 'error': '...'}.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_flight_statusA | Look up one specific flight by its IATA flight number, for the current day or a given date. Returns flight status plus scheduled, estimated and actual times, terminal, gate, baggage belt and delay minutes for both ends, with the operating flight ordered ahead of its codeshares. Use this when the question names a flight number; use flights_with_airline to browse an airline's flights, or historical_flights_by_date for past dates. |
| flights_with_airlineA | Return live flights for one airline, optionally narrowed to a single flight status. Returns flight number, airline, departure and arrival airports with timezones, scheduled departure time, status, delay, terminal and gate. Use this to survey an airline's current activity; use get_flight_status when you already know the flight number. |
| historical_flights_by_dateA | Return flights that already operated on a past date, with optional airline and route filters. Returns flight date, status, flight number, airline, and both airports with their scheduled times. Requires the Basic plan or higher. Use this for past dates only: use flight_arrival_departure_schedule for today and future_flights_arrival_departure_schedule for later dates. |
| flight_arrival_departure_scheduleA | Return today's arrival or departure board for an airport, optionally filtered by airline name. Returns airline, flight number, scheduled, estimated and actual times, terminals, gates and departure delay per flight. Covers the current day only: for any later date use future_flights_arrival_departure_schedule instead. |
| future_flights_arrival_departure_scheduleA | Return the scheduled arrival or departure board for an airport on a specific future date. Covers any date from tomorrow through about 12 months ahead, including the next 7 days. Returns airline, flight number, scheduled times, arrival airport, terminal, gate and aircraft model. Use flight_arrival_departure_schedule for today's board instead. |
| random_aircraft_typeA | Return a random sample of aircraft types from the Aviationstack reference catalog. Each record has aircraft_name and iata_code. Records are drawn from a random offset, so repeated calls return different rows. This samples the catalog and cannot look up a specific model: there is no search parameter. |
| random_airplanes_detailed_infoA | Return a random sample of individual airplanes from the reference catalog. Each record has model name and code, series, production line, registration number, owner, age, engine type and count, delivery date and first flight date. Records are drawn from a random offset, so repeated calls return different aircraft. Sampling only: there is no lookup by registration. |
| random_countries_detailed_infoA | Return a random sample of countries from the reference catalog. Each record has country name, capital, continent, ISO2, ISO3 and numeric ISO codes, FIPS code, currency name and code, phone prefix and population. Records are drawn from a random offset, so repeated calls return different countries. Sampling only: there is no lookup by country name or code. |
| random_cities_detailed_infoA | Return a random sample of cities from the reference catalog. Each record has city name, IATA code, country ISO2, latitude, longitude, timezone, GMT offset and geoname id. Records are drawn from a random offset, so repeated calls return different cities. Sampling only: there is no lookup by city name. |
| list_airportsA | List airports from the reference catalog, one page at a time, with optional text search. Each record has airport name, IATA and ICAO codes, city IATA code, country name and ISO2, timezone and GMT offset, alongside a pagination block carrying limit, offset and total. Use search to resolve an airport name to the IATA code the flight tools expect. |
| list_airlinesA | List airlines from the reference catalog, one page at a time, with optional text search. Each record has airline name, IATA and ICAO codes, callsign, operational status, country name and ISO2, alongside a pagination block carrying limit, offset and total. Use search to resolve an airline name to the IATA code the flight tools expect. |
| list_routesA | List scheduled routes, one page at a time, filtered by any combination of airline, departure airport and arrival airport. Each record has airline IATA and ICAO codes, flight number, and departure and arrival airport codes, alongside a pagination block carrying limit, offset and total. This says which routes exist, not whether a flight is operating: use get_flight_status for that. Requires the Basic plan or higher. |
| list_taxesA | List aviation taxes from the reference catalog, one page at a time, with optional text search. Each record has tax id, tax name and the associated IATA code, alongside a pagination block carrying limit, offset and total. This is static reference data, not fares or amounts charged on a booking. Requires a paid plan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_flight_status_lookup | Generate a plan for checking the status of one specific flight. |
| plan_airline_flight_lookup | Generate a concise plan for querying live flights for an airline. |
| plan_future_schedule_lookup | Generate a plan for querying an airport's scheduled arrival or departure board on a future date, from tomorrow through about 12 months ahead. |
| plan_reference_data_lookup | Generate a plan for exploring airport/airline/route/tax reference data. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server_metadata | Static metadata about this Aviationstack MCP server. |
| aviationstack_endpoints | Available Aviationstack API endpoints used by tools. |
TDQS
Scored across 13 tools
Each flight tool is scoped by a distinct combination of temporal window and entity: specific flight, airline activity, past-date search, today's airport board, or future airport board. The descriptions explicitly cross-reference alternatives, and the reference tools separately cover airports, airlines, routes, taxes, aircraft types, airplanes, countries, and cities.
All names are snake_case and readable, but the action style is mixed: get_flight_status, flights_with_airline, historical_flights_by_date, flight_arrival_departure_schedule, future_flights_arrival_departure_schedule, random_*, and list_*. The list_* and random_* families are consistent internally, but the flight tools do not follow a single verb_noun convention.
The 13 tools cover flight queries plus several reference catalogs without becoming unwieldy. Each tool maps to a distinct endpoint or use case, and the count sits comfortably in the appropriate range.
Core flight workflows are covered: current flight status, airline activity, historical flights, and today/future airport boards, along with airport, airline, and route lookups. However, aircraft types, individual airplanes, countries, and cities are random-sample only with no targeted lookup or search, leaving notable gaps for specific reference queries.