Fr24api MCP server

Read from the package source without running it. The installed server may list more.

• get_airline_info

  Returns airline name, ICAO and IATA codes. REQUIRED: icao code must be provided and non-empty.

• get_airport_info_full

  Returns detailed airport information: full name, ICAO and IATA codes, localization, elevation, country, city, state, timezone details. REQUIRED: code must be provided and non-empty.

• get_airport_info_light

  Returns airport name, ICAO and IATA codes. REQUIRED: code must be provided and non-empty.

• get_flight_summary_count

  Returns the number of flights for a given flight summary query. IMPORTANT: flight_datetime_from and flight_datetime_to are required, and at least one additional search parameter should be provided.

• get_flight_summary_full

  Returns comprehensive timings and locations of aircraft takeoffs and landings, including detailed flight, aircraft, and operator information. Both real-time and extensive historical data are available. Data is available starting from 2024-04-07 and will be extended further in the near future. IMPORTANT: flight_datetime_from and flight_datetime_to are required, and at least one additional search pa

• get_flight_summary_light

  Returns key timings and locations of aircraft takeoffs and landings alongside all primary flight, aircraft, and operator information. Both real-time and historical data are available. Data is available starting from 2024-04-07 and will be extended further in the near future. IMPORTANT: flight_datetime_from and flight_datetime_to are required, and at least one additional search parameter (other tha

• get_flight_tracks

  Returns positional tracks of a specific flight. REQUIRED: flight_id must be provided and non-empty.

• get_historic_flight_events_full

  Returns selected historical flight events (gate_departure, takeoff, cruising, airspace_transition, resuming_flightplan, descent, landed, gate_arrival), with detailed information, sorted by event_timestamp and grouped by flight_id. REQUIRED: flight_ids and event_types must be provided and non-empty.

• get_historic_flight_events_light

  Returns selected historical flight events (gate_departure, takeoff, cruising, airspace_transition, resuming_flightplan, descent, landed, gate_arrival), sorted by event_timestamp and grouped by flight_id. REQUIRED: flight_ids and event_types must be provided and non-empty.

• get_historic_flights_count

  Returns number of historical aircraft flight positions. IMPORTANT: Timestamp is required, and at least one additional search parameter (other than limit) must be provided and non-empty.

• get_historic_flights_positions_full

  Returns historical aircraft flight movement information including latitude, longitude, speed, and altitude alongside key flight and aircraft information such as origin, destination, callsign, registration and aircraft type. FR24 API provides access to historical flight data, dating back to May 11, 2016, depending on the user's subscription plan. IMPORTANT: Timestamp is required, and at least one a

• get_historic_flights_positions_light

  Returns historical aircraft flight movement information including latitude, longitude, speed and altitude. FR24 API provides access to historical flight data, dating back to May 11, 2016, depending on the user's subscription plan. IMPORTANT: Timestamp is required, and at least one additional search parameter (other than limit) must be provided and non-empty.

• get_live_flights_count

  Returns the count of real-time aircraft flights matching the specified criteria. IMPORTANT: At least one search parameter (other than limit) must be provided and non-empty. Choose from: bounds, flights, callsigns, registrations, painted_as, operating_as, airports, routes, aircraft, altitude_ranges, squawks, categories, data_sources, airspaces, gspeed.

• get_live_flights_positions_full

  Returns real-time aircraft flight movement information including latitude, longitude, speed, and altitude alongside key flight and aircraft information such as origin, destination, callsign, registration and aircraft type. IMPORTANT: At least one search parameter (other than limit) must be provided and non-empty. Choose from: bounds, flights, callsigns, registrations, painted_as, operating_as, air

• get_live_flights_positions_light

  Returns real-time aircraft flight movement information including latitude, longitude, speed, and altitude. IMPORTANT: At least one search parameter (other than limit) must be provided and non-empty. Choose from: bounds, flights, callsigns, registrations, painted_as, operating_as, airports, routes, aircraft, altitude_ranges, squawks, categories, data_sources, airspaces, gspeed.

• Code scan9 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 253 days ago4/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Fr24api: common questions

Is Fr24api MCP server safe?

With care: it is graded C, so read the findings first (68/100). Read the Fr24api safety report

How do I install Fr24api?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Fr24api need an API key?

Yes. The registry entry asks for FR24_API_KEY.

Is Fr24api maintained?

The last commit was 264 days ago (2026-01-22). The latest release is v1.0.1.

What can I use instead of Fr24api?

Servers from other publishers that do the same job: Variflight MCP server, Open Meteo MCP server and Agentic Ledger MCP server. Compare all Fr24api alternatives.