Faa Traffic Delays MCP Server

What faa-traffic-delays-mcp-server does

faa-traffic-delays-mcp-server MCP server exposes FAA air traffic management data through six MCP tools. The data covers the National Airspace System, US airport conditions, the Air Traffic Control System Command Center operations plan, and ATCSCC advisories.

The airport status tool accepts FAA or ICAO identifiers and reports conditions such as ground stops, Ground Delay Programs, arrival and departure delays, closures, deicing, restrictions, and runway configuration. A request can contain up to 25 distinct airports per processed call. The active-events tool provides a nationwide view, including en-route Airspace Flow Programs, with severity ordering and event-type counts.

Agents can also inspect planned terminal and en-route initiatives, list advisories for a UTC date, and retrieve the full text of a specific advisory. The reference tool explains event types, traffic-management terminology, ARTCC codes, pacing airports, and identifier formats.

How it works

The server reads the FAA NAS Status feed behind nasstatus.faa.gov and the ATCSCC advisories database. It returns structured MCP tool results rather than requiring an agent to parse the source pages directly.

Airport inputs may be supplied as an array or comma-separated string. FAA and ICAO forms for the same airport count as one item, and the response identifies any omitted airports when the request exceeds the processing cap. Airport records preserve request order and can include identifiers, coordinates, ARTCC information, active event details, and runway data when available.

Active events can be filtered by types including ground stops, Ground Delay Programs, Airspace Flow Programs, arrival delays, departure delays, closures, closure NOTAMs, and deicing. Advisory listings support UTC dates, categories, control elements, literal case-insensitive subject or detail searches, limits, and offsets. Advisory numbers are interpreted together with their UTC date because numbering restarts each day.

Setup and configuration

The package can run as a stdio process or as a local Streamable HTTP server. A public hosted endpoint is available at https://faa-traffic-delays.caseyjhand.com/mcp. The repository also provides installation paths for Claude Desktop, Cursor, and VS Code, and publishes an npm package under @cyanheads/faa-traffic-delays-mcp-server.

No required environment variables or configuration values are documented in the supplied material. The server is also associated with a Docker container package, although specific container commands are not provided here.

Tools and capabilities

• faa_delays_get_airport_status: Checks current conditions for requested US airports and returns event, delay, closure, deicing, runway, and location fields where available.
• faa_delays_list_active_events: Lists active NAS events, optionally filtered by type, with severity ordering, counts, timing, delay information, and advisory references.
• faa_delays_get_operations_plan: Returns expected later-day programs and initiatives with time qualifiers, UTC times, likelihood, announcements, and a related advisory reference.
• faa_delays_get_advisory: Retrieves one advisory by number and UTC date, including subject, control element, timing, and full text.
• faa_delays_list_advisories: Lists advisories newest first and supports date, category, control-element, text, and pagination filters.
• faa_delays_list_reference: Supplies definitions and identifier guidance for interpreting returned aviation data.

Limitations and notes

faa-traffic-delays-mcp-server MCP server depends on the availability and format of FAA source services. If the en-route feed cannot be read, Airspace Flow Program data may be omitted with a notice; a request for only that event type can fail instead. Advisory page failures are reported as service-unavailable or contract-changed errors.

Advisory text longer than 50,000 characters is truncated and includes truncation information. An unknown airport invalidates the complete airport-status request. An advisory number that is not present returns found: false with guidance to list advisories first. Some fields, including pacing-airport data and announcements, may be omitted with a notice when their source cannot be read.