Skip to main content
Glama
Sign In
mavlink-mcp

mavlink-mcp

by hieutachi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mavlink-mcp

No user-submitted related servers found.

    Related Servers

    • ardupilot-mavlink-mcp

      rmeadomavic
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with an ArduPilot vehicle in real-time via MAVLink, including reading state, inspecting and changing parameters, switching flight modes, diagnosing arming failures, and gated arming/disarming.
      31 PyPI
      4
      MIT

    • mavforge-mcp

      msmith626
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to identify and diagnose ArduPilot flight controllers over MAVLink, reading status, parameters, backups and diffs, and running guided calibrations. It is read-only by default, with human-approved, read-back-verified parameter changes and identity-checked backups gated behind explicit flags.
      10
      GPL 3.0

    • tello-mcp

      Denisijcu
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects a local LLM to a DJI Tello drone via UDP, enabling natural language flight planning and execution with safety-focused separation of plan and execution, plus a full simulator for development.
      -

    • Betaflight MCP

      bvandevliet
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to control Betaflight flight controllers over serial via MSP and CLI, providing real-time sensor reads, full CLI access, and auto-generated variable tools for configuration and tuning.
      100
      24 npm
      3
      AGPL 3.0
    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

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: read operations (get_flight_mode, get_capabilities, get_telemetry, get_connection_status), safety actions (arm, disarm), and navigation commands (takeoff, land, hold, return_to_launch, goto_location, fly_mission). No overlap or ambiguity.

    Naming Consistency4/5

    Most tools use a consistent verb_noun pattern with snake_case (e.g., get_flight_mode, get_telemetry). Action verbs are single words (arm, disarm, takeoff, land, hold) except return_to_launch and goto_location, which are phrases. The pattern is clear and predictable, with only minor deviation.

    Tool Count5/5

    12 tools is well-scoped for a drone control server. It covers essential read capabilities, safety, and navigation without being excessive. Each tool has a clear role and contributes to a complete workflow.

    Completeness4/5

    The toolset covers core drone operations: reading state, arming, disarming, takeoff, landing, holding, returning, going to a location, and flying missions. Minor gaps exist, such as no direct parameter setting or mode change tool, but the core workflows are fully supported and the guardrails are well-integrated.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources