flightradar

The FlightRadar MCP Server exposes three tools that integrate with MCP-enabled clients to provide real-time flight tracking data via AviationStack. get_flight_data returns detailed information for a specific flight using its IATA or ICAO code, including airline, aircraft, and key timestamps. search_flights allows querying flights by criteria such as airline, departure/arrival airports, and flight status, returning a list of matching results. get_flight_status provides a human-readable status summary for a given flight, useful for conversations and quick status checks. To use these tools, configure the server in your MCP client settings (for example Claude) with the Node.js command and the path to the built server index.js, and supply your AviationStack API key through the AVIATIONSTACK_API_KEY environment variable. Once configured, you can issue natural-language prompts like “What is the status of flight BA855?” or “Show me British Airways flights from PRG today” and receive structured flight information and summaries from the server.

Prerequisites:

• Node.js version 14 or higher
• npm version 6 or higher
• An AviationStack API key (get one at aviationstack.com)

Installation steps:

1. Clone the repository: git clone https://github.com/Cyreslab-AI/flightradar-mcp-server.git cd flightradar-mcp-server

2. Install dependencies: npm install

3. Build the server: npm run build

4. Create MCP configuration for your environment (example path shown below). In Claude/Claude Desktop, add a server entry that points to the built index.js and includes your AviationStack API key:

   • Ensure the path to the built server is correct, e.g. /path/to/flightradar-mcp-server/build/index.js
   • Set the environment variable AVIATIONSTACK_API_KEY to your API key

5. Start the server as part of your MCP environment (the exact start command depends on your hosting environment). The server is designed to be invoked by MCP clients with the command and arguments configured above.

Notes and tips:

• Ensure AVIATIONSTACK_API_KEY is kept secret and not committed to version control.
• If you modify the build output path, update the mcp_config accordingly.
• If you encounter API rate limits, consider upgrading your AviationStack plan or caching results where appropriate.
• The MCP server relies on the AviationStack API; if the API key is invalid or missing, requests will fail gracefully with helpful error messages.
• For Claude integration, place the configuration under the appropriate settings path for your platform as documented in the README.