Skip to main content
Glama
Flightradar24

Flightradar24 MCP Server

Official
by Flightradar24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Flightradar24 MCP Server

No user-submitted related servers found.

    Related Servers

    • Flightradar24 MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Provides access to real-time and historical flight data from Flightradar24 API, enabling users to track live aircraft positions, query flight histories, and retrieve comprehensive aviation information including aircraft, airline, and airport details.
      15
      7 npm
      MIT
    • AirLabs MCP Server by airlabs-co

      AirLabs MCP Serverofficial

      airlabs-co
      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
      130 npm
      MIT

    • mcp-flightstats

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      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.
      MIT

    • Flight MCP Server

      sragss
      F
      license
      Not graded
      quality
      D
      maintenance
      A real-time flight tracking interface for LLMs that connects AI assistants to live aircraft data from ADS-B Exchange, enabling searches by location, specific flight tracking, military aircraft monitoring, and aviation pattern discovery.
      4
      -
    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

    A3.8/5.0

    Scored across 15 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear light/full/count variants serving different purposes. However, the similarity between live and historic position tools, and between flight summary and tracks, may cause minor confusion. Descriptions help differentiate them, so overall boundary clarity is good.

    Naming Consistency5/5

    All tools follow a consistent 'get_' prefix followed by descriptive noun phrases, with modifiers like 'light', 'full', and 'count' used uniformly. The naming pattern is predictable and uniform across the set.

    Tool Count5/5

    With 15 tools, the set is well-scoped for a flight tracking API. It covers live and historical data, summaries, tracks, events, and reference info without being excessive. Each tool serves a clear purpose.

    Completeness4/5

    The tool surface is comprehensive, covering live and historical positions, counts, summaries, tracks, and reference data. Minor gaps exist, such as no direct flight lookup by ID (only tracks) and no airport/airline search by name, but these are not significant for common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources