Skip to main content
Glama

Related Servers

Alternatives to flightops-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with access to real-time flight data, airport schedules, delays, and aviation reference databases through natural language queries.
      12
      191 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides aviation weather data (METAR, TAF, station search) with a unique assess_conditions tool that returns flight category, confidence, and an escalation gate to indicate when human review is needed.
      4
      46 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to ask what aircraft are flying near a location, track a specific flight's live position, route, aircraft details and photo, and surface emergency-squawking or military aircraft. It exposes four tools (flights_near, track_flight, emergencies, military_aircraft) backed by merged volunteer ADS-B networks and a global snapshot.
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to look up live flight status and timetables, create and manage signed-webhook flight subscriptions, inspect delivery attempts and events, and search the API documentation. Tools are exposed to any MCP client such as Claude, Cursor, or VS Code, with read-only, write, and destructive operations clearly marked.
      15
      21 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI assistants with real-time and forecast airport intelligence, including security wait times, FAA delays, EU border queues, lounge and terminal info, aviation weather, and baggage performance for over 8,000 airports.
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues