Skip to content

Airport Delays (FAA Airport Status) MCP

Airport delays today from the FAA: ground stops, ground delay programs, closures, trip check.

build.protocol_tooling.mcp

What our last check of Airport Delays (FAA Airport Status) MCP found

Stork connects to every MCP server it lists that has a public endpoint and records what came back: every week when the server answers without an account, every month otherwise. These are the results for Airport Delays (FAA Airport Status) MCP.

Result
AnsweredThe endpoint completed an MCP handshake with no account.
Last checked
The server reported version 1.0.0.
Tools listed
3
Context cost of the tool definitions
About 410 tokensWhat Airport Delays (FAA Airport Status) MCP adds to a model's context before you ask anything, unless your client loads tools on demand. Estimated from the length of the definitions at 4 characters a token.
Test call
Returned a resultOn 17 November 2026 we called one read-only tool, airport_delays_now, once with a plain test input. It returned content. We did not judge whether the content was right.

Changes to the tool definitions

We have seen no change to Airport Delays (FAA Airport Status) MCP's tool definitions since we began checking it.

A check is one initialize request and one tools/list request from Stork's servers, with no account. Where a server answers without an account we also call one read-only tool once. Neither can tell you that every tool does its job or that the server is safe to connect.

Install Airport Delays (FAA Airport Status) MCP in your MCP client

Airport Delays (FAA Airport Status) MCP is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.

  1. Locate your client's MCP config file.
    • Cursor: ~/.cursor/mcp.json
    • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
    • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
    • VS Code: Settings → Extensions → MCP
    • Windsurf: Settings → MCP Servers
  2. Add Airport Delays (FAA Airport Status) MCP to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing mcpServers object.
  3. Restart your client so it picks up the new server.
  4. Verify — ask the assistant to list available tools; Airport Delays (FAA Airport Status) MCP's tools should appear.
{
  "mcpServers": {
    "airport-delays--faa-airport-status--mcp": {
      "url": "https://airport-delays-faa-status-mcp.lipmichal.workers.dev/mcp"
    }
  }
}

Maintain Airport Delays (FAA Airport Status) MCP, or spotted a wrong detail on this page? Report a problem and we will correct it. Corrections are free.

Install Airport Delays (FAA Airport Status) MCP in Cursor

Open ~/.cursor/mcp.json in your editor, paste the snippet above into mcpServers, save, and restart Cursor. Airport Delays (FAA Airport Status) MCP will show up in the assistant's tool list on next launch.

Install Airport Delays (FAA Airport Status) MCP in Claude Desktop (macOS)

Open ~/Library/Application Support/Claude/claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (macOS). Airport Delays (FAA Airport Status) MCP will show up in the assistant's tool list on next launch.

Install Airport Delays (FAA Airport Status) MCP in Claude Desktop (Windows)

Open %APPDATA%\Claude\claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (Windows). Airport Delays (FAA Airport Status) MCP will show up in the assistant's tool list on next launch.

Install Airport Delays (FAA Airport Status) MCP in VS Code

Open Settings → Extensions → MCP in your editor, paste the snippet above into mcpServers, save, and restart VS Code. Airport Delays (FAA Airport Status) MCP will show up in the assistant's tool list on next launch.

Tools exposed by Airport Delays (FAA Airport Status) MCP

Once installed, Airport Delays (FAA Airport Status) MCP exposes the following MCP tools to your AI assistant. Each tool can be called directly by the assistant whenever its capability is relevant to your prompt.

  • airport_delays_now

    All US airports with an active FAA event right now: ground stops, ground delay programs (average and maximum delay, reason such as weather or volume, end time), general arrival and departure delays with trend, airport closures and deicing, sorted worst first, plus airspace flow programs.

  • airport_status

    FAA delay status of one US airport, by IATA code (JFK), ICAO code (KJFK), airport name or city (Newark, O'Hare, Denver): any ground stop, ground delay program, arrival or departure delay, closure or deicing with reason, minutes and end time, or a clear statement that the FAA reports no delay there;

  • airport_delays_check_trip

    Check every airport on an itinerary (origin, connections, destination; 1 to 8 airports) for FAA ground stops, ground delay programs, delays and closures in one call.

Transport

Airport Delays (FAA Airport Status) MCP supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.

streamable-http

Other Model Context Protocol servers in the same space as Airport Delays (FAA Airport Status) MCP. Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.

Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.