About fr24api-mcp
fr24api-mcp is an MCP server that provides access to the Flightradar24 API for real-time and historical flight data. It suits AI assistants that need aircraft positions, flight histories, and airport or airline reference details.
Key features
- 01Live aircraft positions with multiple filter options
- 02Historical flight data from May 11, 2016 onward
- 03Flight summaries with takeoff and landing information
- 04Detailed positional tracks for a specific flight
- 05Airline and airport reference information lookup
Use cases
- 01Finding live flights within a geographic area
- 02Reviewing historical flights at a given airport
- 03Retrieving takeoff and landing summaries or tracks for a flight
MCP support
The project is an MCP server that exposes flight position, historical, summary and airport tools to MCP clients such as Claude Desktop.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @flightradar24/fr24api-mcpFR24_API_KEYSecretYour API key for Flightradar24 APILocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
15Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | number | No | Limit of results. Recommended, unless needed. Max 30000. |
| bounds | string | No | Coordinates defining an area. Order: north, south, west, east (comma-separated float values). |
| gspeed | string | No | Flight ground speed in knots (single value or range, e.g., 120-140, 80). |
| routes | string | No | Flights between airports/countries (e.g., SE-US, ESSA-JFK). Max 15. |
| flights | string | No | Flight numbers (comma-separated values, max 15). |
| squawks | string | No | Squawk codes in hex format (comma-separated). |
| aircraft | string | No | Aircraft ICAO type codes (comma-separated, max 15). |
| airports | string | No | Airports (IATA/ICAO/ISO 3166-1 alpha-2) or countries. Use format: [direction:]<code>. Directions: inbound, outbound, both. |
| airspaces | string | No | Flight information region in lower or upper airspace. |
| callsigns | string | No | Flight callsigns (comma-separated values, max 15). |
| categories | string | No | Categories of Flights (comma-separated: P, C, M, J, T, H, B, G, D, V, O, N). |
| painted_as | string | No | Aircraft painted in an airline's livery (ICAO code, comma-separated, max 15). |
| data_sources | string | No | Source of information (comma-separated: ADSB, MLAT, ESTIMATED). |
| operating_as | string | No | Aircraft operating under an airline's call sign (ICAO code, comma-separated, max 15). |
| registrations | string | No | Aircraft registration numbers (comma-separated values, max 15). |
| altitude_ranges | string | No | Flight altitude ranges in feet (e.g., 0-3000, 5000-7000). |
Details
From the project READMEFlightradar24 MCP Server
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
Installation
Via npm
npm install -g @flightradar24/fr24api-mcp
Prerequisites
- Node.js: Version 18.0.0 or higher
- 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_herewith 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,aircraftsort: 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
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
Support
- Documentation: https://fr24api.flightradar24.com
- Issues: GitHub Issues
- API Support: Contact Flightradar24 API 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.