Travel

Flighty Airports

flighty-pp-cli

Every Flighty Airports meltdown map feature, plus cross-airport intelligence no web page can answer.

Printed by @SomSamantray (Som Samantray)

Install

npx — recommended

npx -y @mvanhorn/printing-press-library install flighty

Installs the CLI binary and the agent skill (Claude Code, Codex, Cursor, Gemini CLI, Copilot, and more). Add --cli-only or --skill-only for one half. Requires Node.

Hermes

hermes skills install mvanhorn/printing-press-library/cli-skills/pp-flighty --force

From the Hermes CLI. Inside a chat session use /skills install with the same path.

OpenClaw

Install the pp-flighty skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-flighty. The skill defines how its required CLI can be installed.

Paste this to your OpenClaw agent — the skill describes how to install its CLI.

Claude Desktop

This CLI ships an MCPB bundle. Download the latest release .mcpb and double-click it — Claude Desktop walks you through the install.

View source on GitHub →

Every Flighty Airports meltdown map feature, plus cross-airport intelligence no web page can answer.

Live status, METAR weather, performance, and flight boards for 156 tracked airports — parsed straight from Flighty's SSR payload with no app install, no API key, and no login. Then it goes further than the site: network-wide rankings, airline footprints, route checks, healthy alternates, and change diffs, all from a local SQLite mirror that keeps working offline.

Learn more at Flighty Airports.

Created by @SomSamantray (Som Samantray).

Quick Start

# See which airports are melting down right now
flighty-pp-cli airports list --status MAJOR_ISSUES --json

# Full status, weather (raw METAR), and today's performance for one airport
flighty-pp-cli airports show den --json

# Rank the network — the web map never ranks
flighty-pp-cli airports worst --region Europe --limit 5 --json

# Find one flight across arrivals and departures boards
flighty-pp-cli airports find-flight den UA5072 --json

# Mirror the catalog locally for offline search and cross-airport commands
flighty-pp-cli sync --resources airports --full

Unique Features

These capabilities aren't available in any other tool for this API.

Cross-airport intelligence

airports worst — Rank the network's airports right now by cumulative delay and cancellations — the web map color-codes but never ranks.

When an agent needs 'which airports are worst right now', this answers in one command instead of scraping the map.
```
flighty-pp-cli airports worst --region Europe --limit 5 --json
```
airports airline — One airline's delay/cancel/divert footprint aggregated across every synced airport — impossible per-airport on the site.

Travel agents and ops folks ask 'which airline is the worst offender across my hubs today' — this answers it network-wide.
```
flighty-pp-cli airports airline UA --json
```
airports compare — Side-by-side status, delays, warnings, and flight rules for two airports.

Choosing between alternates (SFO vs OAK) is a two-entity question the site cannot express.
```
flighty-pp-cli airports compare sfo oak --json
```
airports route — Both directions of one origin-destination pair's delay/cancel/divert stats, joined from each side's disrupted routes.

Route data exists only from one airport's perspective; this shows both ends of the same route.
```
flighty-pp-cli airports route sfo den --json
```
airports nearby — Distance-ranked nearby airports, flagging which have normal operations right now.

When your airport is melting down, 'where else can I fly from' is the immediate follow-up.
```
flighty-pp-cli airports nearby sfo --healthy-only --limit 3 --json
```

Flight board intelligence

airports find-flight — Find one flight by number across arrivals and departures boards — status, original vs actual time, gate, belt, terminal.

The 'when is my flight actually leaving' question answered in one deterministic command.
```
flighty-pp-cli airports find-flight den UA5072 --json
```

Local state that compounds

airports diff — What changed since the last sync: status transitions, new/cleared warnings, delay deltas.

Monitors and writers need 'what changed since this morning' — the numbers reset upstream, local history persists.
```
flighty-pp-cli airports diff --json
```

Recipes

Morning meltdown sweep

flighty-pp-cli airports list --status MAJOR_ISSUES --json --select iata,city,status,warnings

One line of JSON naming every airport in serious trouble right now.

Pre-flight check

flighty-pp-cli airports show den --json --select airportWeather.flightRulesTitle,today.departurePerformance.onTime.percentage,warnings

Flight rules, on-time rate, and active warnings for your departure airport before you leave.

Find your flight's real departure

flighty-pp-cli airports find-flight den UA5072 --json

Status, original vs actual time, and gate for one flight number across both boards.

Rank Europe's worst hubs

flighty-pp-cli airports worst --region Europe --limit 5 --json

Magnitude-ranked by cumulative delay and cancellations — the web map never ranks.

Where else can I fly from

flighty-pp-cli airports nearby sfo --healthy-only --limit 3 --json

Nearest airports with normal operations when your home airport is melting down.

Usage

Run flighty-pp-cli --help for the full command reference and flag list.

Paths & environment variables

This CLI separates local files into four path kinds:

Kind	Contents
`config`	User-editable settings such as `config.toml` and saved profiles
`data`	Durable local data: `credentials.toml`, `data.db`, cookies, browser-session proof files, and other auth sidecars
`state`	Runtime state such as persisted queries, jobs, and `teach.log`
`cache`	Regenerable HTTP/cache files

Each kind resolves independently. The ladder is:

Per-kind env var: FLIGHTY_CONFIG_DIR, FLIGHTY_DATA_DIR, FLIGHTY_STATE_DIR, or FLIGHTY_CACHE_DIR
--home <dir> for this invocation
FLIGHTY_HOME for a flat relocated root
XDG env vars: XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME
Platform defaults matching existing installs

For containers and agent sandboxes, prefer a single relocated root:

export FLIGHTY_HOME=/srv/flighty
flighty-pp-cli doctor

Under FLIGHTY_HOME=/srv/flighty, the four dirs resolve to /srv/flighty/config, /srv/flighty/data, /srv/flighty/state, and /srv/flighty/cache.

MCP servers do not receive CLI flags from the host. Put relocation in the host env block:

{
  "mcpServers": {
    "flighty": {
      "command": "flighty-pp-mcp",
      "env": {
        "FLIGHTY_HOME": "/srv/flighty"
      }
    }
  }
}

Precedence matters in fleets: an ambient per-kind variable such as FLIGHTY_DATA_DIR overrides an explicit --home for that kind. Use FLIGHTY_HOME or the per-kind variables for durable fleet relocation; treat --home as the weaker per-invocation lever.

Relocation is one-way. Unsetting FLIGHTY_HOME does not move files back to platform defaults, and doctor cannot find credentials left under a former root. Move the files manually before unsetting relocation variables.

Existing installs keep working because the platform-default rung matches the legacy layout. On the first auth write, stored secrets leave config.toml and are consolidated into credentials.toml under the data directory. Run flighty-pp-cli doctor --fail-on warn to check path and credential-location warnings in automation.

Commands

airports

Airport status, delays, weather, and flight boards

flighty-pp-cli airports arrivals - Show the live arrivals board for an airport
flighty-pp-cli airports departures - Show the live departures board for an airport
flighty-pp-cli airports list - List the tracked airports with live delay status (meltdown map catalog)
flighty-pp-cli airports show - Show live status, weather, and performance for one airport
flighty-pp-cli airports tv - List disrupted airports from the TV dashboard (same catalog, status-sorted)

Self-learning loop

This CLI caches per-question discovery so repeat queries skip the walk and structurally similar queries get answered via entity substitution. The loop also self-captures: every invocation is journaled locally, and failed-flag corrections plus fresh teaches surface as candidates on the next recall for confirm/reject judgment. Agents call recall before discovery and fire teach & after answering. See the ## Automatic learning section in SKILL.md for the full protocol.

flighty-pp-cli recall <query> - Look up cached resources for a query before running discovery
flighty-pp-cli teach - Record a query -> resource mapping (silent on success, safe to background with &)
flighty-pp-cli learnings list - Inspect taught rows
flighty-pp-cli learnings forget <query> - Undo a teach
flighty-pp-cli learnings candidates - List auto-captured candidates awaiting confirm/reject
flighty-pp-cli learnings stats - Local loop metrics: recall hit rate, teach-to-reuse, playbook resolution, candidate counts
flighty-pp-cli teach-pattern - Install a query/resource template up front
flighty-pp-cli teach-lookup - Add an entity mapping (e.g. country code, team alias) for pattern substitution

Pass --no-learn or set FLIGHTY_NO_LEARN=true to disable the loop for deterministic flows.

The local store's schema version stamp is one-way: once this version of flighty-pp-cli opens the database, older binaries refuse it with a version error — upgrade the binary rather than downgrading.

Output Formats

# Human-readable table (default in terminal, JSON when piped)
flighty-pp-cli airports list

# JSON for scripting and agents
flighty-pp-cli airports list --json
# Filter to specific fields
flighty-pp-cli airports list --json --select id,slug,name

# Dry run — show the request without sending
flighty-pp-cli airports list --dry-run

# Agent mode — JSON + compact + no prompts in one flag
flighty-pp-cli airports list --agent

Agent Usage

This CLI is designed for AI agent consumption:

Non-interactive - never prompts, every input is a flag
Pipeable - --json output to stdout, errors to stderr
Filterable - --select <field>[,<field>...] returns only fields you need
Previewable - --dry-run shows the request without sending
Read-only by default - this CLI does not create, update, delete, publish, send, or mutate remote resources
Offline-friendly - sync/search commands can use the local SQLite store when available
Agent-safe by default - no colors or formatting unless --human-friendly is set

Exit codes: 0 success, 2 usage error, 3 not found, 5 API error, 7 rate limited, 10 config error.

Health Check

flighty-pp-cli doctor

Verifies configuration and connectivity to the API.

Configuration

Run flighty-pp-cli doctor to see the resolved config, data, state, and cache directories. The platform-default config path is ~/.config/flighty-pp-cli/config.toml; --home, FLIGHTY_HOME, and per-kind env vars can relocate it.

Static request headers can be configured under headers; per-command header overrides take precedence.

Troubleshooting

Not found errors (exit code 3)

Check the resource ID is correct
Run the list command to see available items

API-specific

airports show says airport not found — Use the IATA code (den) or exact slug (denver-intl-den); run flighty-pp-cli airports list to see tracked airports
Cross-airport commands (worst, nearby, airline, diff) return empty — Run flighty-pp-cli sync --resources airports --full first — those commands read the local mirror
Data looks stale — Re-sync or use --data-source live on commands that support it; Flighty updates the site continuously

Discovery Signals

This CLI was generated with browser-captured traffic analysis.

Target observed: https://flighty.com/airports
Capture coverage: 0 API entries from 6 total network entries
Reachability: standard_http (65% confidence)
Protocols: html_scrape (55% confidence)
Auth signals: none

Sources & Inspiration

This CLI was built by studying these projects and resources:

flighty-mcp-server (CPLX) — TypeScript
flighty-mcp (LukasHaas) — Python
flighty-mcp (sailingnaturali) — Python

Generated by CLI Printing Press