iNAV MCP Server
Related Servers
Alternatives to iNAV MCP Server
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 gradedqualityFmaintenanceEnables natural language analysis of ArduPilot flight logs (.bin files) via AI chat apps like Claude Desktop, Cursor, and VS Code, providing explanations and answering questions about flight issues.30 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseBqualityCmaintenanceEnables 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.10012 npm2AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to build, flash, and communicate with STM32 hardware over SWD and serial, including multi-board management, live memory monitoring, and hardware sequences.25MIT
- 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.28 npmMIT
TDQS
Scored across 35 tools
Most tools have clear, distinct purposes with thorough descriptions. A few pairs (connect/board_info, backup_config/save_and_reboot) overlap slightly, but the descriptions clarify the differences, so confusion is unlikely.
The majority follow a verb_noun pattern (e.g., list_serial_ports, set_flight_mode), but there are notable exceptions: why_wont_it_arm is a sentence, connect/disconnect/diagnose are bare verbs, and cli/cli_batch are nouns. This inconsistency makes the set feel less predictable.
35 tools is well above the typical heavy range. While the domain is complex, many tools could be consolidated (e.g., read_sensors/read_gps/read_rc_channels or multiple set_* tools), making the surface feel bloated.
The tool set covers the full workflow: connection discovery, config backup/restore, aircraft setup, mode assignment, calibration, diagnostics, failsafe, GPS, navigation, and tuning. No significant gaps are apparent for the intended fixed-wing use case.