F
licenseNot graded
qualityD
maintenanceEnables natural language interaction with Betaflight FPV drone flight controllers for configuration, PID tuning, sensor monitoring, VTX control, and blackbox management through Claude AI.
4
-
ardupilot-mcp
by furkanisikay
Related Servers
Alternatives to ardupilot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for inspecting PX4 ULog flight logs, enabling AI assistants to understand, debug, and reason about drone systems.3MIT
- AlicenseNot gradedqualityFmaintenanceEnables natural language control of ArduPilot drones via MAVLink, supporting arm, takeoff, mode changes, and mission uploads.9GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables 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 PyPI4MIT
- AlicenseAqualityBmaintenanceLets an MCP client read PX4 SITL .ulg logs and answer why a flight failed or underperformed — failsafes, arming reasons, estimator validity versus simulator ground truth, and how late PX4 followed offboard velocity setpoints. It also lists, searches, scans and plots topics, messages and parameters across logs, replacing hand-written pyulog scripts.12MIT
- AlicenseAqualityBmaintenanceEnables configuration, diagnostics, and troubleshooting of iNAV fixed-wing flight controllers over USB via Claude.3544 PyPI2MIT
TDQS
A3.7/5.0
Scored across 12 tools
Disambiguation4/5
Most tools have clearly distinct roles: analyze_log (full diagnostics) vs incident_timeline (time ordering) vs log_summary (cheap orientation) vs list_events (raw decoded events) vs query_timeseries (raw drilling) are well differentiated. Minor potential overlap between analyze_log's findings and incident_timeline's tags, but descriptions make the boundary clear.
Naming Consistency4/5
All names use snake_case and most follow a verb_noun pattern (analyze_log, get_params, compare_logs, load_param_file, query_timeseries, recommend_tuning, list_events, list_checks). A few are noun phrases (incident_timeline, forum_report, vehicle_profile, log_summary), a minor deviation but still readable and predictable.
Tool Count5/5
12 tools is well within the ideal range and each earns its place in a log-diagnosis workflow: entry point (log_summary), deep analysis (analyze_log), temporal/raw access (incident_timeline, list_events, query_timeseries), config (get_params, load_param_file, compare_logs), and reporting/advisory (forum_report, recommend_tuning).
Completeness4/5
Covers the core diagnostic lifecycle: orient, diagnose, temporalize, inspect parameters/config, compare flights, and produce reports/advisories. Minor gaps: no direct visualization/export beyond the text plot in forum_report, and recommend_tuning is advisory-only with no apply path, but these are reasonable for a read/diagnose server.
Maintenance
ActivityMaintained
ResponsivenessSyncing