flightops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLIGHTOPS_OPENSKY_CLIENT_ID | No | OpenSky API client ID (from Account → API Client at opensky-network.org). Required to unlock the traffic and movement tools. | |
| FLIGHTOPS_OPENSKY_CLIENT_SECRET | No | OpenSky API client secret, paired with FLIGHTOPS_OPENSKY_CLIENT_ID. Required to unlock the traffic and movement tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use this server for questions about the operational state of an airport and the traffic around it.
Rules that the tools will enforce:
Resolve identifiers first.
resolve_airportis offline and free; it returns ICAO (ident), IATA, name and coordinates. Never guess a coordinate.airport_live_traffic,airport_movementsanddisruption_triagespend OpenSky API credits. Prefer onedisruption_triagecall over three separate ones.airport_weatherneeds no credentials and no credits.Absence of data is not evidence. Each payload lists
unknowns; if it is non-empty, say so instead of concluding that operations are normal.This server is advisory. It reports observations and flags; it never authorises an operational decision.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_airportA | Resolve an airport from an ICAO/IATA code or a name fragment. |
| airport_live_trafficA | Return aircraft currently within a radius of an airport. |
| airport_movementsA | List estimated arrivals and/or departures for an airport. |
| airport_weatherA | Return the latest METAR and TAF for an airport, plus impact flags. |
| disruption_triageA | Assess whether an airport is currently disrupted: weather, traffic, movements. |
| upstream_statusA | Report upstream health, credit spend and credential state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a fairly distinct concern (weather, live traffic, movements, health, airport lookup), and descriptions explicitly separate free vs credit-spending calls. The main overlap is disruption_triage, which internally duplicates weather/traffic/movements, so an agent must judge whether to call the composite or the primitives — the description guides this but does not eliminate the choice. airport_live_traffic vs airport_movements is also a subtle distinction (aircraft currently present vs inferred arrivals/departures) that takes careful reading.
All names are snake_case and readable, but the pattern is mixed: three tools use an 'airport_' prefix while disruption_triage, upstream_status, and resolve_airport do not. Verb style is also inconsistent — resolve_airport is verb_noun while the rest are noun-first (noun_noun or adjective_noun), so there is no predictable verb_noun convention to rely on.
Six tools is well within a tight, purposeful scope for an airport-centric flight ops server. Every tool has a clear job: reference lookup, weather, traffic, movements, composite triage, and diagnostics — no filler or near-duplicates that could be consolidated without losing function.
The read-only airport situational-awareness domain is well covered: weather, live traffic, movements, composite severity, identifier resolution, and upstream/credential diagnostics with an explicit escape hatch for failures. Minor gaps remain — no aircraft/callsign-level lookup, no historical or delay-statistics access beyond the one-hour movements window, and no way to pull deeper airport metadata from resolve_airport.