Fr24api MCP logo

Fr24api MCP

Query live and historical Flightradar24 flight data, tracks, summaries, airline records, and airport details through MCP.

Install Fr24api MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "fr24api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@flightradar24/fr24api-mcp"
      ],
      "env": {
        "FR24_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @flightradar24/fr24api-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

The fr24api-mcp MCP server connects MCP clients to the Flightradar24 API for live and historical aviation data. It exposes tools for aircraft positions, flight counts, flight summaries, individual flight tracks, airline information, and airport records. Use it when an AI assistant needs filtered flight activity, historical snapshots, route data, or aviation reference details. Running it requires Node.js 18 or later and a Flightradar24 API key.

Use cases

  • Find live flights within a geographic area
  • Compare historical aircraft positions at a timestamp
  • Retrieve takeoff and landing summaries for a route
  • Inspect the positional track of a specific flight
  • Look up airline and airport details

Key features

  • Live aircraft positions with light and full detail
  • Historical positions and flight counts
  • Filtered flight summaries with sorting and limits
  • Detailed tracks for specific flight IDs
  • Airline and airport reference lookups

Tools13

What Fr24api MCP lets your agent do. Expand a tool for its parameters.

Self-reported~243 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

26/26 checks healthy over the last 101d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · @flightradar24/fr24api-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars30Stargazers on the source repository.
npm downloads4.1kPackage downloads in the last 30 days.
Last commit10mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed13Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Fr24api MCP works

What fr24api-mcp does

The fr24api-mcp MCP server exposes Flightradar24 aviation data as MCP tools. It supports current aircraft-position queries, historical position lookups, flight summaries, detailed tracks for an identified flight, and reference data for airlines and airports.

Live position tools can return either basic or full information, and a separate count tool reports how many flights match the query. Filters can include geographic bounds, flight numbers, callsigns, aircraft registrations, airports, routes, aircraft ICAO types, altitude ranges, and flight categories. Live queries can return up to 30,000 results when a limit is used.

Historical position tools accept a Unix timestamp and offer light, full, and count variants. Historical data is available from May 11, 2016, according to the project documentation.

How it works

The server communicates with MCP clients over its standard command-line process. An MCP client sends tool calls, and the server uses the supplied Flightradar24 API key to query the Flightradar24 API.

Flight summary tools search a UTC datetime interval using flight_datetime_from and flight_datetime_to in ISO format. They can filter by flights, callsigns, registrations, airports, routes, and aircraft. Full and light variants return different levels of summary detail, while the count variant returns the number of matching flights. Summary results can be sorted ascending or descending and limited to 20,000 records.

The get_flight_tracks tool requires a Flightradar24 flight ID in hexadecimal format. Airline lookup requires an ICAO code, while both airport tools accept an IATA or ICAO airport code.

Setup and configuration

Install the package globally with npm:

Terminal
npm install -g @flightradar24/fr24api-mcp

Node.js 18 or newer is required. Obtain a Flightradar24 API key, then provide it through the FR24_API_KEY environment variable. For Claude Desktop, configure the server with npx and set the variable in the client configuration:

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

Other MCP clients can launch it directly with FR24_API_KEY=your_api_key_here npx @flightradar24/fr24api-mcp. Restart Claude Desktop after changing its configuration. When running a locally built copy, use Node.js with the path to build/index.js.

Tools and capabilities

The fr24api-mcp MCP server provides:

  • Live positions with light or full aircraft details
  • Live flight counts using the same filtering options
  • Historical positions and counts for a requested timestamp
  • Full and light flight summaries, plus summary counts
  • Detailed tracks for a specific flight ID
  • Airline information by ICAO code
  • Basic or full airport information, including location, elevation, and timezone in the full response

Build from source with npm install followed by npm run build after cloning the repository.

Limitations and notes

A live position query requires at least one filter, such as bounds, flights, callsigns, registrations, airports, routes, aircraft, altitude ranges, or categories. Several list-style filters accept at most 15 values, and live results have a documented maximum of 30,000. Historical position requests require a timestamp, while summary requests require both start and end datetimes. Summary results have a maximum limit of 20,000. API access depends on a valid Flightradar24 API key and the applicable Flightradar24 API service.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Fr24api MCP

fr24api-mcp is an MCP server that connects AI assistants to the Flightradar24 API. Its main tools retrieve live and historical aircraft positions, flight counts, flight summaries, tracks, airline details, and airport information. It requires a Flightradar24 API key and supports installation through npm with Node.js 18 or newer.

Install it with npm using `npm install -g @flightradar24/fr24api-mcp`. Node.js 18 or newer is required. You must also provide a Flightradar24 API key through the `FR24_API_KEY` environment variable before launching the server.

Add an `fr24api` entry to Claude Desktop's MCP configuration with `npx` as the command, `@flightradar24/fr24api-mcp@latest` as its argument, and `FR24_API_KEY` in the environment. Restart Claude Desktop after saving the configuration.

It can retrieve live and historical aircraft positions, matching flight counts, flight summaries, detailed tracks for a flight ID, airline information by ICAO code, and basic or full airport information by IATA or ICAO code.

Use a historical positions tool with the required Unix `timestamp`, or use a flight summary tool with UTC start and end datetimes. Optional filters include flights, callsigns, registrations, airports, routes, and aircraft, depending on the tool.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFr24api MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/fr24api-mcp?style=directory)](https://allmcps.com/mcp/fr24api-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/fr24api-mcp"><img src="https://allmcps.com/api/badge/fr24api-mcp?style=directory" alt="Fr24api MCP on AllMCPs" /></a>