Fr24api Mcp
Expose Flightradar24 real-time and historical flight data to your agent while building aviation dashboards, trackers, or travel-adjacent features.
Overview
Flightradar24 API MCP is a MCP server for the Build phase that provides agent access to real-time and historical Flightradar24 API flight data.
What is this MCP server?
- npm package @flightradar24/fr24api-mcp v1.0.1 with stdio transport
- Requires FR24_API_KEY for authenticated Flightradar24 API access
- Surfaces real-time and historical flight data to MCP clients
- Maintained by Flightradar24 org on GitHub
- MCP server schema 2025-09-29
- Server version 1.0.1
- One required secret environment variable: FR24_API_KEY
- npm registry package @flightradar24/fr24api-mcp
Community signal: 18 GitHub stars.
What problem does it solve?
You are building a flight-aware feature but constantly context-switch between API docs and your agent to test queries and map responses.
Who is it for?
Indie devs shipping aviation or travel-side projects who already have a Flightradar24 API key and use Claude Code or Cursor daily.
Skip if: Builders with no flight data needs, or teams that must avoid third-party aviation API cost and compliance constraints.
What do I get? / Deliverables
With FR24_API_KEY configured, your agent invokes MCP tools for live and historical flight data while you implement integrations in one workspace.
- Agent-callable Flightradar24 real-time flight queries
- Historical flight data access during feature development
- Faster API exploration without leaving the agent session
Recommended MCP Servers
Journey fit
Third-party flight API wiring happens during Build when you integrate external data into your product backend or agent tools. Integrations subphase is for MCP bridges to vendor APIs like Flightradar24 that your app or agent calls during development.
How it compares
Vendor flight-data MCP bridge, not an open-world browser automation or generic scraping skill.
Common Questions / FAQ
Who is fr24api-mcp for?
Developers integrating Flightradar24 into apps or agent workflows who want MCP-native access to real-time and historical flight endpoints.
When should I use fr24api-mcp?
During Build integrations while prototyping queries, validating payloads, and wiring flight features before Ship hardening.
How do I add fr24api-mcp to my agent?
Install @flightradar24/fr24api-mcp from npm, set the required secret FR24_API_KEY, register stdio MCP in your client, and invoke tools from the agent.