Provides tools for interacting with FlightAware AeroAPI v4, enabling real-time flight status lookups, historical flight tracks, airport arrivals/departures, and current in-air flight positions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@flightaware What's the current status of flight UA123?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FlightAware MCP — wraps FlightAware AeroAPI v4 (aeroapi.flightaware.com)
Part of Pipeworx — an MCP gateway connecting AI agents to 1573+ live data sources.
Tool | Description |
| Get real-time flight status for a flight number or tail number: origin/destination airports, scheduled/estimated/actual departure & arrival times, current status, and aircraft type. Returns a flights[] array (one flight ident can map to several dated flights). Example: flightaware_flight_status({ ident: "UAL123", _apiKey: "your-key" }) |
| Get the historical position track (breadcrumb trail of lat/lon/altitude/groundspeed points) for a specific flight. The |
| List flights at an airport — arrivals and/or departures with scheduled & actual times. The |
| Get the current/last-known position of an in-air flight: latitude, longitude, altitude, groundspeed, heading and timestamp. The |
Related MCP server: general-agentic-management-mcp
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"flightaware": {
"url": "https://gateway.pipeworx.io/flightaware/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/flightaware/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1573+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"flightaware": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-flightaware"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-flightawareIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Flightaware data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
FlightStats MCP — wraps the Cirium FlightStats Flex API (api.flightstats.com/flex)
Aviationstack MCP — global flight + airport + airline data
Flights MCP — wraps OpenSky Network API (free, no auth required)
Airports MCP — wraps AirportGap API (free, no auth required)