ardupilot-mavlink-mcp — Claude Code MCP server: features and setup
ardupilot-mavlink-mcp is an MCP server for Claude Code that connects an AI agent to an ArduPilot vehicle via MAVLink. Inspects live telemetry and troubleshoots prearm issues.
MIT ★ 5 updated 2026-08-03
claude mcp add ardupilot-mavlink-mcp -- uvx ardupilot-mavlink-mcpWhat ardupilot-mavlink-mcp does
The server connects to an ArduPilot instance over TCP, UDP, or serial connections. A dedicated reader thread collects the MAVLink stream and caches telemetry, allowing the agent to retrieve orientation, battery level, GPS fixes, and flight modes without blocking the connection.
It handles live prearm troubleshooting by reading incoming STATUSTEXT notices and the returned COMMAND_ACK responses directly from the link. The tool also looks up and updates flight parameters against echoed PARAM_VALUE confirmations and changes vehicle modes by name.
All actuation tools stay disabled by default. Modifying parameters, switching modes, or arming in SITL demands the --enable-actuation flag. Interacting with actual hardware also requires passing --allow-real-vehicle. Writing to ARMING_CHECK is rejected unconditionally. The server runs on Python 3.10 or newer.
What it helps with
- Inspect live ArduPilot telemetry data from an asynchronous link cache
- Identify why a vehicle refuses to arm using real-time prearm status logs
- Update autopilot parameters confirmed via echoed parameter messages
- Switch vehicle flight modes by name across ArduCopter and other variants
Example prompts for the agent
- Check the ArduPilot link status and show current battery voltage
- Read recent statustext messages to explain why arming failed
- Switch the current flight mode to GUIDED
How to install ardupilot-mavlink-mcp
Platform CLI
claude mcp add ardupilot-mavlink-mcp -- uvx ardupilot-mavlink-mcpuvx runs the command named after the package; if the README names another one, use uvx --from ardupilot-mavlink-mcp <command>
Platform CLI
codex mcp add ardupilot-mavlink-mcp -- uvx ardupilot-mavlink-mcpuvx runs the command named after the package; if the README names another one, use uvx --from ardupilot-mavlink-mcp <command>
Config file
{
"mcpServers": {
"ardupilot-mavlink-mcp": {
"command": "uvx",
"args": [
"ardupilot-mavlink-mcp"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from ardupilot-mavlink-mcp <command>
Config file
{
"servers": {
"ardupilot-mavlink-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"ardupilot-mavlink-mcp"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from ardupilot-mavlink-mcp <command>
Platform CLI
gemini mcp add ardupilot-mavlink-mcp uvx ardupilot-mavlink-mcpuvx runs the command named after the package; if the README names another one, use uvx --from ardupilot-mavlink-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about ardupilot-mavlink-mcp
How to install ardupilot-mavlink-mcp in Claude Code?
Run the command claude mcp add ardupilot-mavlink-mcp -- uvx ardupilot-mavlink-mcp.
What does ardupilot-mavlink-mcp do?
It bridges an active ArduPilot MAVLink stream to MCP tools so an agent can read live state, inspect parameters, diagnose failed arm attempts, and update modes.
What is required to run ardupilot-mavlink-mcp?
You need Python 3.10 or higher and an active ArduPilot SITL instance or flight controller. Enabling actuation and arming requires adding --enable-actuation and --allow-real-vehicle flags.