Skip to main content
Glama
Flightradar24 MCP Server

Flightradar24 MCP Server

Official

Flightradar24 MCP Server

npm version License: MIT

This Model Context Protocol (MCP) server provides access to the Flightradar24 API for real-time and historical flight data. This server enables AI assistants like Claude to access comprehensive aviation data including live flight positions, aircraft information, airport details, and flight histories.

Features

  • Real-time Flight Tracking: Get live positions of aircraft worldwide

  • Historical Flight Data: Access flight data dating back to May 11, 2016

  • Comprehensive Flight Information: Detailed aircraft, airline, and airport data

  • Flexible Filtering: Search by callsigns, registrations, routes, aircraft types, and more

  • Flight Summaries: Complete takeoff and landing information

  • Aircraft Tracks: Detailed positional tracking for specific flights

Related MCP server: airplanes-live-mcp

Installation

Via npm

npm install -g @flightradar24/fr24api-mcp

Prerequisites

  1. Node.js: Version 18.0.0 or higher

  2. Flightradar24 API Key: Get your API key from https://fr24api.flightradar24.com

Configuration

Claude Desktop Integration

Add this configuration to your claude_desktop_config.json file:

{
  "mcpServers": {
    "fr24api": {
      "command": "npx",
      "args": ["@flightradar24/fr24api-mcp@latest"],
      "env": {
        "FR24_API_KEY": "your_api_key_here"
      }
    }
  }
}

Important Notes:

  • Replace your_api_key_here with your actual Flightradar24 API key

  • Restart Claude Desktop after adding the configuration

  • If installed locally, use the full path: "command": "node", "args": ["/path/to/build/index.js"]

Other MCP Clients

For other MCP clients, run the server directly:

FR24_API_KEY=your_api_key_here npx @flightradar24/fr24api-mcp

Available Tools

Live Flight Data

get_live_flights_positions_light

Get real-time aircraft positions with basic information.

Parameters (at least one required):

  • bounds: Geographic area (north,south,west,east coordinates)

  • flights: Flight numbers (comma-separated, max 15)

  • callsigns: Flight callsigns (comma-separated, max 15)

  • registrations: Aircraft registrations (comma-separated, max 15)

  • airports: Airport codes with optional direction (e.g., "inbound:JFK,outbound:LAX")

  • routes: Flight routes (e.g., "JFK-LAX,LHR-CDG")

  • aircraft: Aircraft ICAO types (comma-separated, max 15)

  • altitude_ranges: Altitude ranges in feet (e.g., "0-3000,30000-40000")

  • categories: Flight categories (P,C,M,J,T,H,B,G,D,V,O,N)

  • limit: Maximum results (default: no limit, max: 30000)

get_live_flights_positions_full

Get real-time aircraft positions with comprehensive flight details. Same parameters as above

get_live_flights_count

Get count of live flights matching criteria. Same parameters as above

Historical Flight Data

get_historic_flights_positions_full

Get historical flight positions with full details.

Required Parameters:

  • timestamp: Unix timestamp for historical snapshot

Optional Parameters: Same as live flight parameters

get_historic_flights_positions_light

Get historical flight positions with basic information. Same parameters as above

get_historic_flights_count

Get count of historical flights. Same parameters as above

Flight Summaries

get_flight_summary_full

Get comprehensive flight takeoff/landing information.

Required Parameters:

  • flight_datetime_from: Start datetime (YYYY-MM-DDTHH:MM:SSZ)

  • flight_datetime_to: End datetime (YYYY-MM-DDTHH:MM:SSZ)

Optional Parameters:

  • flights, callsigns, registrations, airports, routes, aircraft

  • sort: Sort order ("asc" or "desc")

  • limit: Maximum results (max: 20000)

get_flight_summary_light

Get essential flight takeoff/landing information. Same parameters as above

get_flight_summary_count

Get count of flights in summary query. Same parameters as above (without sort/limit)

Specific Flight Data

get_flight_tracks

Get detailed positional tracks for a specific flight.

Required Parameters:

  • flight_id: Flightradar24 flight ID (hexadecimal)

Reference Data

get_airline_info

Get airline information by ICAO code.

Required Parameters:

  • icao: Airline ICAO code

get_airport_info_light

Get basic airport information.

Required Parameters:

  • code: Airport IATA or ICAO code

get_airport_info_full

Get comprehensive airport information including location, elevation, timezone.

Required Parameters:

  • code: Airport IATA or ICAO code

Usage Examples

Find flights around New York

Get live flights in the New York area with bounds: 41.0,-74.5,40.5,-73.5

Track specific flight

Get flight tracks for flight ID: 2f4a8b3c

Historical data

Get historical flights at JFK airport on timestamp 1640995200 with airports: inbound:JFK

Flight summary

Get flight summary from 2024-01-01T00:00:00Z to 2024-01-02T00:00:00Z for route JFK-LAX

Development

Building from Source

git clone https://github.com/flightradar24/fr24api-mcp.git
cd fr24api-mcp
npm install
npm run build

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Add tests if applicable

  5. Submit a pull request

Support

License

MIT License - see LICENSE file for details.

Changelog

1.0.2

  • fix: flight summary 14 days prompt

  • release file update to asure trusted publisher works (#6)

1.0.1

Release to MCP Registry

1.0.0

  • Initial public release

  • Comprehensive flight data access

  • Real-time and historical data support

  • Enhanced parameter validation

  • Improved error handling

Available Tools

15 tools
get_airline_infoA

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

Inputs: icao (required).

get_airport_info_fullA

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.

Inputs: code (required).

get_airport_info_lightB

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

Inputs: code (required).

get_flight_summary_countA

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.

Inputs: flight_datetime_to (required), flight_datetime_from (required), routes, flights, +6 more.

get_flight_summary_fullA

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 parameter (other than sort and limit) should be provided.

Inputs: flight_datetime_to (required), flight_datetime_from (required), sort, limit, +8 more.

get_flight_summary_lightA

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 than sort and limit) should be provided.

Inputs: flight_datetime_to (required), flight_datetime_from (required), sort, limit, +8 more.

get_flight_tracksA

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

Inputs: flight_id (required).

get_historic_flight_events_fullA

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.

Inputs: flight_ids (required), event_types (required).

get_historic_flight_events_lightA

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.

Inputs: flight_ids (required), event_types (required).

get_historic_flights_countA

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.

Inputs: timestamp (required), limit, bounds, gspeed, +13 more.

get_historic_flights_positions_fullA

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 additional search parameter (other than limit) must be provided and non-empty.

Inputs: timestamp (required), limit, bounds, gspeed, +13 more.

get_historic_flights_positions_lightB

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.

Inputs: timestamp (required), limit, bounds, gspeed, +13 more.

get_live_flights_countA

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.

Inputs: limit, bounds, gspeed, routes, +12 more.

get_live_flights_positions_fullA

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, airports, routes, aircraft, altitude_ranges, squawks, categories, data_sources, airspaces, gspeed.

Inputs: limit, bounds, gspeed, routes, +12 more.

get_live_flights_positions_lightA

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.

Inputs: limit, bounds, gspeed, routes, +12 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear light/full/count variants serving different purposes. However, the similarity between live and historic position tools, and between flight summary and tracks, may cause minor confusion. Descriptions help differentiate them, so overall boundary clarity is good.

    Naming Consistency5/5

    All tools follow a consistent 'get_' prefix followed by descriptive noun phrases, with modifiers like 'light', 'full', and 'count' used uniformly. The naming pattern is predictable and uniform across the set.

    Tool Count5/5

    With 15 tools, the set is well-scoped for a flight tracking API. It covers live and historical data, summaries, tracks, events, and reference info without being excessive. Each tool serves a clear purpose.

    Completeness4/5

    The tool surface is comprehensive, covering live and historical positions, counts, summaries, tracks, and reference data. Minor gaps exist, such as no direct flight lookup by ID (only tracks) and no airport/airline search by name, but these are not significant for common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Provides access to real-time and historical flight data from Flightradar24 API, enabling users to track live aircraft positions, query flight histories, and retrieve comprehensive aviation information including aircraft, airline, and airport details.
      15
      9 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with access to real-time flight data, airport schedules, delays, and aviation reference databases through natural language queries.
      12
      189 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language and tool-based access to live flight status, airport departure/arrival boards, and scheduled flight timetables via the Cirium FlightStats Flex API.
      326 npm
      MIT