flightradar24-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FR24_API_KEY | Yes | Your FR24 API key for the Flightradar24 API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_flight_dataA | Get real-time position data for a specific flight that is currently airborne, by flight number or callsign. Uses the FR24 live flight positions endpoint, so it only returns a result while the flight is in the air. For completed, scheduled, or historical flights, use get_flight_summary instead. |
| search_flightsA | Search for currently airborne flights using the FR24 live flight positions endpoint. At least one filter (besides limit and detail_level) must be provided. |
| get_flight_summaryA | Get takeoff/landing history (flight summary) for flights in a date/time window, optionally filtered by flight number, callsign, registration, airport, route, or aircraft type. Covers completed flights; use get_flight_data for flights currently in the air. |
| get_flight_tracksA | Get the detailed position track (a series of timestamped lat/lon/altitude/speed points) for one specific flight, identified by its FR24 flight ID (fr24_id). Get the fr24_id from get_flight_data, search_flights, or get_flight_summary first. |
| get_airport_dataA | Get information about an airport by its exact IATA or ICAO code. |
| get_airline_dataA | Get an airline's name and IATA code by its ICAO code. |
| get_flights_in_zoneA | Get all currently airborne flights within a specified geographic bounding box. |
| get_api_usageA | Get a summary of FR24 API credit usage per endpoint. Note: FR24 rate-limits this endpoint to 1 call per minute. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools clearly target distinct resources: airports, airlines, tracks, live positions, and historical summaries. The only mild overlap is between search_flights and get_flights_in_zone, both returning currently airborne flights, but their filter-based vs bounding-box approaches are described clearly enough to avoid significant confusion.
The naming follows a mostly consistent get_X pattern (get_flight_data, get_airport_data, get_flight_summary). Minor deviations include search_flights using a different verb and the singular/plural variation between get_flight_tracks and get_flights_in_zone, but the overall convention remains predictable.
Eight tools is well-scoped for a flight tracking and aviation data server. Each tool covers a meaningful query type without unnecessary redundancy, and the count fits comfortably within the ideal range.
The core workflows are covered: live flight search, live flight detail, historical summaries, detailed tracks, airport lookup, airline lookup, and API usage. Minor gaps such as airport arrival/departure boards or aircraft-specific data are absent, but common FR24 use cases are fully workable.