Overview

Real-time air traffic management status from the FAA Air Traffic Control System Command Center (ATCSCC), read from the NAS Status feed behind nasstatus.faa.gov and the ATCSCC advisories database. Check US airports for ground stops, Ground Delay Programs, delays, and closures; list every active event nationwide, en-route Airspace Flow Programs included; read the operations plan for later in the day; list the advisories issued on a UTC date, canceled and past programs included; and read the full advisory behind each one. Runs as a stdio process, a local Streamable HTTP server, or the public hosted endpoint above.

Tools

Capability reference

faa_delays_get_airport_status _tool

• airports: 1–100 submitted codes, each a 3-character FAA identifier (SEA) or ICAO code (KSEA, PHNL), case-insensitive, as an array or comma-separated string. Every code is validated before fetching; an unknown code fails the whole call as unknown_airport. FAA/ICAO equivalents use one slot; the first 25 distinct airports are processed in order. cap: 25, processedCount, and omittedAirports identify the exact canonical remainder to pass in the next call
• One row per airport, in request order: status (closed, ground_stop, ground_delay_program, delays, restrictions_only, no_active_events), listedInFeed, airportName, artcc, latitude / longitude, requestedAs for an ICAO input, and each active event: groundStop, groundDelayProgram with programStartTime and a per-15-minute delayProfile, arrivalDelay / departureDelay, closure, closureNotam, deicing
• artcc comes from the NASR directory and matches the ARTCC codes in a program's includedFacilities; an airport the feed doesn't list takes its coordinates from the directory too. runwayConfiguration (runways and arrivalRatePerHour) appears only for listed airports; isPacingAirport and timezone are omitted, with a notice, when the pacing-airport list can't be read
• PHX reported as US/Mountain uses effective timezone: "America/Phoenix" and retains reportedTimezone: "US/Mountain"; every other airport/value pair stays as reported

faa_delays_list_active_events _tool

• Optional event_types filter over ground_stop, ground_delay_program, airspace_flow_program, arrival_delay, departure_delay, airport_closure, closure_notam, deicing (aliases gs, gdp, afp); rows are sorted by severity, with reason, delay figures, times, and an advisory reference where the FAA links one
• totalActive and countsByType cover the whole feed before the filter; shown / appliedEventTypes echo what was returned. ground_delay_program rows add programStartTime beside the current revision's startTime, and airspace_flow_program rows carry afp detail (constrained area, departure and arrival filters, altitudes, delay profile)
• enRouteFeed (ok, unavailable, format_changed) reports whether Airspace Flow Programs were read. An en-route failure omits them with a notice rather than failing the call, unless they are the only type requested

faa_delays_get_operations_plan _tool

• No input; terminalPlanned and enRoutePlanned items carry text, timeQualifier (after, until, by, between), timeUtc (HHMM with no date), and likelihood (possible, probable, expected)
• announcements lists current ATCSCC announcements ([] when none; absent, with a notice, when the list can't be read); advisory references the full plan text for faa_delays_get_advisory

faa_delays_get_advisory _tool

• advisory_number (1–999) and date (UTC, YYYY-MM-DD; MM/DD/YYYY accepted), taken from a faa_delays_list_advisories row or an advisory reference's number and date; numbers restart at 1 each UTC day, and past advisories stay readable
• Returns title, controlElement, subject, effectiveTime and sentAt as the advisory prints them (DDHHMM-DDHHMM, YY/MM/DD HH:MM, on operations plans and reroutes too), and the full text; a number the database doesn't hold returns found: false with guidance that points to faa_delays_list_advisories
• Text past 50,000 characters is cut and reported through truncated and totalChars; page failures surface as advisory_service_unavailable or advisory_contract_changed

faa_delays_list_advisories _tool

• Optional query matches a literal, case-insensitive substring in subject or any details line before paging, combined with the other filters. For a named FCA in the plan, use query: "FCA005"; appliedQuery echoes the trimmed filter
• date (UTC, YYYY-MM-DD; MM/DD/YYYY accepted; no later than tomorrow; omitted → today), optional categories (ground_stop, ground_delay_program, airspace_flow_program, ctop, route, other; aliases gs, gdp, afp) and control_element (an airport by FAA or ICAO code, an ARTCC, or DCC for national advisories), limit 1–200 (default 50) and offset
• Rows newest first: number and date for faa_delays_get_advisory, controlElement, subject, details (a reroute's or flow constrained area's name, constrained area, and valid period), and sentAt (ISO 8601 UTC); totalCount counts every match and nextOffset is present while more remain
• Without categories the list also carries the CDM compression advisories the FAA files under no category; a date with no advisories, or a filter that matches none, returns an empty list with a notice

faa_delays_list_reference _tool

• topic: event_types, terms, artccs, pacing_airports, or identifiers
• Only pacing_airports calls the FAA (live, cached 6 hours); identifiers also reports the bundled NASR airport directory's cycle date and airport count

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

FAA-specific:

• Reads the NAS Status feed (nasstatus.faa.gov/api) and the ATCSCC advisories database (www.fly.faa.gov/adv), keyless; FAA status and NASR airport data are US federal works in the public domain (17 U.S.C. §105)
• Airport codes are checked against a bundled snapshot of the FAA NASR airport directory, with ICAO codes mapped to FAA identifiers (KSEA → SEA, PHNL → HNL), so a mistyped code fails instead of reading as a quiet airport; the same directory supplies each airport's ARTCC, and its coordinates when the feed doesn't list it
• Feeds are cached in process for 60 seconds (the pacing-airport list for 6 hours) and requests to each FAA host are paced; an expired snapshot is never served when a refresh fails
• Tolerant parsing of the undocumented feed: an unreadable row is skipped and counted in the notice; unreadable event objects, planned lists, and invalid delay profiles are named as unknown sections. Wrong-typed scalar fields are dropped and logged. Delay-profile sequences must be exactly 1 through N after sorting, so missing intervals never shift later delays

Agent-friendly output:

• Typed failure reasons keep an outage (feed_unavailable), a slow or throttled FAA (retry_deadline_exceeded, upstream_rate_limited, pacer_shed), and a format change (feed_contract_changed, not retryable) distinct; recovery hints name the tool to call next, and rate-limit errors carry retryAfter when known
• A secondary FAA list that can't be read (pacing airports, en-route events, announcements) is omitted with a flag or notice instead of failing the call
• fetchedAt dates the snapshot, and a notice flags an arrival or departure delay last updated more than 6 hours earlier, since the FAA feed can keep a delay entry after it lapses
• FAA-authored text (reasons, NOTAMs, comments, announcements, advisory text) is quoted or fenced in content[] so it reads as data, and stays verbatim in structuredContent

Limitations:

• Informational, not operational. No substitute for an official preflight briefing or airline operations data.
• Undocumented upstream. nasstatus.faa.gov/api/* is the dashboard's private backend, with no schema, terms, versioning, or published limits, and it can change without notice. The server fails with feed_contract_changed rather than guess.
• Airport coverage is event-driven. The feed lists only airports with an active event, so runway configuration and arrival rate are unavailable for the rest, and no_active_events means no FAA program, not on-time flights. Per-flight EDCTs are not in the feed.
• En-route row shape is inferred, not observed. Airspace Flow Program rows follow the shape the NAS Status dashboard's own code reads; a mismatch degrades the national list with enRouteFeed: "format_changed" rather than failing it.
• The airport directory is a snapshot. An identifier the FAA assigns after the bundled NASR cycle is rejected as unknown until the next refresh. US airports only.

Getting started

Public Hosted Instance

A public instance is available at https://faa-traffic-delays.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:

{
  "mcpServers": {
    "faa-traffic-delays-mcp-server": {
      "type": "streamable-http",
      "url": "https://faa-traffic-delays.caseyjhand.com/mcp"
    }
  }
}

Self-Hosted / Local

Add the following to your MCP client configuration file.

{
  "mcpServers": {
    "faa-traffic-delays-mcp-server": {
      "type": "stdio",
      "command": "bunx",
      "args": ["@cyanheads/faa-traffic-delays-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with npx (no Bun required):

{
  "mcpServers": {
    "faa-traffic-delays-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cyanheads/faa-traffic-delays-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with Docker:

{
  "mcpServers": {
    "faa-traffic-delays-mcp-server": {
      "type": "stdio",
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/faa-traffic-delays-mcp-server:latest"]
    }
  }
}

For Streamable HTTP, set the transport and start the server:

MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
# Server listens at http://localhost:3010/mcp

Prerequisites

• Bun v1.4.0 or higher (or Node.js v24+).
• No API key or account: the FAA feeds are public.

Installation

1. Clone the repository:

git clone https://github.com/cyanheads/faa-traffic-delays-mcp-server.git

2. Navigate into the directory:

cd faa-traffic-delays-mcp-server

3. Install dependencies:

bun install

4. Configure environment (optional):

cp .env.example .env
# every variable has a default; edit .env only to change transport, logging, or telemetry

Configuration

The server reads no environment variables of its own: the FAA hosts, cache lifetimes, and request pacing are fixed in the services. These framework variables cover transport, logging, and telemetry.

See .env.example for the common framework overrides.

Running the server

Local development

• Build and run the production version:

  sh

  Copy

  # One-time build
  bun run rebuild
  
  # Run the built server
  bun run start:http
  # or
  bun run start:stdio
  

• Run checks and tests:

  sh

  Copy

  bun run devcheck  # Lints, formats, type-checks, and more
  bun run test      # Runs the test suite
  

• Refresh the airport directory from the current FAA NASR cycle (needs network access and the system unzip):

  sh

  Copy

  bun run refresh:airports
  

Project structure

Development guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

• Handlers throw, framework catches — no try/catch in tool logic
• Use ctx.log for logging; FAA feeds are cached in process, not in ctx.state
• Register new tools in allToolDefinitions in src/mcp-server/tools/definitions/index.ts
• Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields

Contributing

Issues are welcome. Run checks and tests before submitting:

bun run devcheck
bun run test

License

This project is licensed under the Apache 2.0 License. See the LICENSE file for details.