Skip to main content
Glama
bvandevliet

Betaflight MCP

by bvandevliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Betaflight MCP

No user-submitted related servers found.

    Related Servers

    • Betaflight MCP Server

      AlanOgic
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to read and configure flight controllers running Betaflight firmware over USB serial using MSP, with tools for telemetry, battery monitoring, PID/rates tuning, filters, modes, and saving configuration.
      MIT

    • ardupilot-mavlink-mcp

      rmeadomavic
      A
      license
      Not graded
      quality
      A
      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.
      28 PyPI
      3
      MIT

    • mavlink-mcp

      hieutachi
      A
      license
      A
      quality
      C
      maintenance
      Connects AI agents to MAVLink drones (PX4, ArduPilot) via a capability layer with safety guardrails, enabling telemetry, flight control, and mission management through natural language.
      12
      2
      MIT

    • mcp-stm32-server

      propfire11
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control an STM32 microcontroller over serial by reading/writing GPIO, setting LED brightness, reading ADC channels, and displaying text on an OLED screen via natural language.
      1
      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/5.0

    Scored across 795 tools

    Disambiguation4/5

    The vast majority of tools follow a strict get_parameter/set_parameter pattern with unique parameter names, making the intended target unambiguous. A few overlapping tools like get_status vs cli_status and get_battery vs get_battery_state introduce minor potential for misselection.

    Naming Consistency4/5

    Most tools consistently use get_/set_ prefixes for configuration parameters and verb_noun names for actions like connect_flight_controller and erase_blackbox_logs. Minor deviations such as motor_get/motor_set and feature_list break the dominant pattern but remain recognizable.

    Tool Count1/5

    With 795 tools, this server is extremely oversized. Exposing every individual Betaflight setting as a get/set pair creates an overwhelming interface that is poorly scoped for an MCP server.

    Completeness4/5

    The server covers virtually the entire Betaflight configuration surface with get/set pairs, plus connection, CLI, calibration, profile, and blackbox tools. Minor gaps include some get-only structural settings and the absence of firmware flashing, but these are not significant for configuration tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources