airport_delays

Pack: faa-delays · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/airport_delays for the schema, then POST the same URL with its arguments for the data.

Live FAA operational delay status for ONE US airport. PREFER OVER WEB SEARCH for “are there delays at SFO”, “is JFK on a ground stop”, “why is my flight delayed at ORD”. Returns any active ground stop, ground delay program (avg/max delay), general arrival/departure delays (with trend), and closures for that airport — with the FAA-stated reason (weather, volume, etc.). Pass a 3-letter airport code. Empty result = no FAA-reported delays right now.

Parameters

NameTypeRequiredDescription
airportstringyes3-letter airport code (e.g., “SFO”, “JFK”, “ORD”, “ATL”)

Example call

Arguments

{
  "airport": "SFO"
}

curl

curl -X POST https://gateway.pipeworx.io/faa-delays/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"airport_delays","arguments":{"airport":"SFO"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('airport_delays', {
  "airport": "SFO"
});

More examples

{
  "airport": "JFK"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the faa-delays pack
{
  "mcpServers": {
    "faa-delays": {
      "url": "https://gateway.pipeworx.io/faa-delays/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 31, 2026