Skip to main content
Glama
Sign In
BACH-AI-Tools

Flightradar24 MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Flightradar24 MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-adsb

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query live ADS-B flight data, including aircraft currently flying near a given latitude/longitude, individual airframes tracked by ICAO hex address or callsign, and military or government aircraft transmitting worldwide. Each tool returns real-time positions with altitude, ground speed, heading, and vertical rate rather than schedules.
      283 npm
      MIT

    • mcp-flightstats

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language and tool-based access to live flight status, airport departure/arrival boards, and scheduled flight timetables via the Cirium FlightStats Flex API.
      14 npm
      MIT

    • FreeFlight

      Ethos6
      A
      license
      Not graded
      quality
      A
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation3/5

    Tools are generally distinct by resource type (airline, airport, flight summaries, tracks, events, positions) and data depth (full/light), but there is significant overlap within categories. For example, get_flight_summary_full and get_flight_summary_light serve similar purposes with varying detail, which could confuse agents about which to select for basic needs. The presence of both full and light versions for multiple endpoints creates redundancy that may lead to misselection.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern with get_ prefixes and descriptive suffixes (e.g., _full, _light, _count). However, there are minor deviations: get_airport_info_full and get_airport_info_light use 'info' while others use more specific terms like 'summary' or 'positions', and get_flight_tracks lacks a suffix, breaking the pattern slightly. Overall, the naming is predictable and readable.

    Tool Count4/5

    With 15 tools, the count is reasonable for a flight data server covering airlines, airports, flights, and historical/live data. It is slightly on the higher side due to duplicate full/light versions, but each tool serves a distinct data depth or resource, making it manageable. The scope justifies the number without feeling overly bloated.

    Completeness4/5

    The toolset provides comprehensive coverage for querying flight data, including airlines, airports, flight summaries, tracks, events, and live/historical positions. Minor gaps exist, such as no tools for updating or deleting data (which may be intentional for a read-only API) and no direct tools for flight scheduling or alerts, but core retrieval operations are well-covered for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources