Ardupilot Mavlink Mcp
by rmeadomaviccommunityv0.1.0
1
An MCP server that connects to an ArduPilot vehicle over MAVLink and lets an agent read vehicle state, inspect and change parameters, switch modes, and read prearm failure messages. It also supports gated arm/disarm actions, with SITL as the primary intended environment.
From the registry: Live ArduPilot control over MAVLink: state, params, modes, prearm diagnosis, gated arm. SITL-first.
Install & configure
Prerequisites
- requiredInstall Python 3.10+Python 3.10 or newer is required to run the MCP server.
- requiredInstall pipxInstall pipx to install and run the ardupilot-mavlink-mcp package as recommended by the README.
$ pipx install ardupilot-mavlink-mcp - requiredStart an ArduPilot vehicle or SITL instanceYou need a reachable ArduPilot MAVLink endpoint. The README recommends developing against local SITL first.
$ sim_vehicle.py -v ArduCopter --console
Install in your client
Paste into the AI you're chatting with — it will figure out the rest
Please install the `ardupilot-mavlink-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Python 3.10+** — Python 3.10 or newer is required to run the MCP server.
- **Install pipx** — Install pipx to install and run the ardupilot-mavlink-mcp package as recommended by the README. Run: `pipx install ardupilot-mavlink-mcp`
- **Start an ArduPilot vehicle or SITL instance** — You need a reachable ArduPilot MAVLink endpoint. The README recommends developing against local SITL first. Run: `sim_vehicle.py -v ArduCopter --console`
Canonical MCP server config (stdio transport):
- command: `ardupilot-mavlink-mcp`
- args: ["--connect","tcp:127.0.0.1:5760"]
Note: The server runs over stdio and connects onward to ArduPilot over MAVLink using a pymavlink connection string. Common examples from the README: tcp:127.0.0.1:5760 for SITL, udp:127.0.0.1:14550, or serial:/dev/ttyACM0:115200. Optional safety flags include --enable-actuation to allow parameter writes, mode changes, and arm/disarm, and --allow-real-vehicle if actuation should be permitted on a non-loopback or serial link.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Note: The server runs over stdio and connects onward to ArduPilot over MAVLink using a pymavlink connection string. Common examples from the README: tcp:127.0.0.1:5760 for SITL, udp:127.0.0.1:14550, or serial:/dev/ttyACM0:115200. Optional safety flags include --enable-actuation to allow parameter writes, mode changes, and arm/disarm, and --allow-real-vehicle if actuation should be permitted on a non-loopback or serial link.
Tools (9)
ardupilot_connect
Connect to a vehicle, with the default being local SITL.
ardupilot_vehicle_state
Read cached vehicle state such as mode, armed status, GPS, battery, attitude, and position.
ardupilot_recent_statustext
Read recent STATUSTEXT and prearm messages to diagnose arming failures.
ardupilot_get_param
Read a single parameter.
ardupilot_set_param
Set a parameter, confirmed by the echoed PARAM_VALUE.
ardupilot_list_params
List parameters, optionally filtered by a glob pattern.
ardupilot_set_mode
Request a flight mode change by mode name.
ardupilot_arm
Arm the vehicle through the safety gate, with confirmation via COMMAND_ACK.
ardupilot_disarm
Disarm the vehicle through the safety gate, with confirmation via COMMAND_ACK.
Prerequisites
- • Python 3.10
Packages
ardupilot-mavlink-mcp
pypiv0.1.0transport: stdio
Details
- Language
- Python
- License
- MIT
- Released
- Jun 22, 2026
- Last commit
- Aug 3, 2026
- Registry name
- io.github.rmeadomavic/ardupilot-mavlink-mcp