Skip to main content
Glama
AlanOgic

Betaflight MCP Server

by AlanOgic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Betaflight MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      15 npm
      3
      AGPL 3.0

    • 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

    • 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.
      4
      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 38 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action purposes (get_/set_ pairs for PID, rates, filters, battery). However, the RC-detection cluster (snapshot_rc_delta, measure_rc_noise, detect_rc_mapping, detect_rc_channel_move) has overlapping sampling purposes, and the battery surface (get_battery, get_battery_state, get_voltage_meters, get_current_meters) requires reading descriptions carefully to distinguish.

    Naming Consistency4/5

    Strong verb_noun convention throughout (get_*, set_*, get_battery_config/set_battery_config, list_serial_ports, save_config, reboot_fc). Minor deviations: connect/disconnect are bare verbs, and select_profile/measure_rc_noise/add consistent enough to stay readable.

    Tool Count2/5

    38 tools is heavy and exceeds the comfortable 3-15 range. While the FC-config domain is genuinely broad, several read-only getters (get_voltage_meters, get_current_meters, get_sensor_config) could be consolidated, pushing this toward over-scoped.

    Completeness4/5

    Core lifecycle is well covered with matched get/set pairs for PID, filters, rates, battery, profiles, plus connection management and RC discovery. Gaps remain: get_advanced_config, get_feature_config, get_modes, and get_sensor_config have no corresponding setters, leaving write paths for those areas missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources