Betaflight MCP
Related Servers
Alternatives to Betaflight MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Betaflight FPV drone flight controllers for configuration, PID tuning, sensor monitoring, VTX control, and blackbox management through Claude AI.4-
- AlicenseNot gradedqualityAmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityFmaintenanceEnables natural language control of ArduPilot drones via MAVLink, supporting arm, takeoff, mode changes, and mission uploads.9GPL 3.0
- AlicenseAqualityCmaintenanceConnects AI agents to MAVLink drones (PX4, ArduPilot) via a capability layer with safety guardrails, enabling telemetry, flight control, and mission management through natural language.122MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI tools like Claude Code and Codex CLI to read and write serial port data, facilitating embedded development workflows such as coding, flashing, and debugging.20MIT
TDQS
Scored across 795 tools
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.
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.
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.
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.