OFFICIAL API

FlightAware

The official FlightAware AeroAPI, in two tools. Flight status takes a flight number or a tail registration and returns every matching operation — scheduled, estimated and actual times, delays, gates and terminals, aircraft, progress, cancelled and diverted flags — with flightaware.com tracking links. The schedule tool lists what actually flies between two airports in a date window. Operational data only, no prices. AeroAPI bills per call, so results are cached for a minute.

2 tools ~1–3 s cache: 1 min FlightAware AeroAPI (official)
Connect

Thirty seconds, any client.

claude mcp add --transport http flightaware https://mcp.wondel.ai/flightaware/mcp

One command in your terminal — the server is available in every Claude Code session.

This server works with Claude, Claude Code, Claude Desktop, Claude Cowork, Cursor, VS Code, Windsurf — and any other MCP client. Stdio-only clients connect through npx mcp-remote.

The Tools

2 tools, fully typed.

Parameters below are transcribed from the server’s own zod schemas — what you see is what the tool validates.

flightaware_flight_status Live or planned status of a flight: scheduled, estimated and actual times, delays, gates and terminals, aircraft, progress, cancelled/diverted flags and flightaware.com tracking links.
Param Type Description
ident * string Flight ident: IATA number (LO281), ICAO number (BAW123) or tail registration (SP-LVD).
max_pages integer
= 1 		AeroAPI result pages to fetch — each page is billed separately.
no_cache boolean
= false 		Force a fresh AeroAPI fetch, bypassing this server’s result cache.
flightaware_search_scheduled Scheduled (future) flights between two airports in a date window: ident, operator, scheduled departure and arrival, aircraft type. No prices.
Param Type Description
origin * string Origin airport IATA or ICAO code (e.g. WAW or EPWA).
destination * string Destination airport IATA or ICAO code.
date_start * date Window start date, YYYY-MM-DD.
date_end * date Window end date, YYYY-MM-DD — exclusive, as AeroAPI defines it.
max_pages integer
= 1 		AeroAPI result pages to fetch — each page is billed separately.
no_cache boolean
= false 		Force a fresh AeroAPI fetch, bypassing this server’s result cache.
Try It

Prompts that just work.

Is LO281 on time today? Which gate does it leave from?

flightaware_flight_status

What flies Warsaw → Heathrow next Monday, and on which aircraft?

flightaware_search_scheduled

Where is the aircraft SP-LVD right now?

flightaware_flight_status

What comes back

flightaware_flight_status · illustrative — the shape is the tool’s, the values are examples 

{
  "source": "flightaware.com/aeroapi",
  "fetchedAt": "2026-07-02T05:12:03.441Z",
  "ident": "LO281",
  "flight_url": "https://www.flightaware.com/live/flight/LO281",
  "count": 1,
  "flights": [
    {
      "ident": "LOT281",
      "ident_iata": "LO281",
      "operator": "LOT",
      "origin": { "code_iata": "WAW", "name": "Warsaw Chopin", "city": "Warsaw", … },
      "destination": { "code_iata": "LHR", "name": "Heathrow", "city": "London", … },
      "scheduled_out": "2026-07-02T05:40:00Z",
      "status": "Scheduled",
      "departure_delay": 0,
      "cancelled": false,
      "diverted": false,
      "track_url": "https://www.flightaware.com/live/flight/id/LOT281-1751400000-airline-0500",
      …
    }
  ]
}

Fetching tools share one envelope — source says where the data came from, fetchedAt says when, query echoes what you asked. FlightAware echoes the ident (or route) instead of a query block. Compact JSON in one text block, exactly how agents like it.

Add FlightAware
to your agent.

mcp.wondel.ai/flightaware/mcp

Authless · Read-only public data · Streamable HTTP at /mcp