mavlink-mcp

01 · What it does

• Arm, take off, goto, move, orbit, land and RTL
• Fly a whole mission from one prompt and report state from live telemetry
• Send camera frames to the model (Gazebo, RTSP or UDP)
• Geofence and GCS-heartbeat failsafe; set_param with safety guards
• Read-only tools are marked readOnlyHint, flight tools destructiveHint

02 · Install

$ python3 -m venv ~/.venvs/drone && source ~/.venvs/drone/bin/activate
$ pip install mavlink-mcp
$ claude mcp add --transport stdio drone -- mavlink-mcp --enable-actuation

1. Flight tools stay off until you pass --enable-actuation; read the README's Safety section first
2. Solid in ArduPilot SITL (beta); not yet flown on real hardware per README. PX4 is detected but flight is refused until its backend lands
3. No SITL: mavlink-mcp --backend fake --enable-actuation runs an in-memory drone
4. pip install "mavlink-mcp[camera]" for an RTSP camera. GETTING_STARTED.md walks a fresh machine to a first SITL flight

03 · Client config (from README)

{
  "mcpServers": {
    "drone": { "command": "mavlink-mcp", "args": ["--enable-actuation", "--camera", "gazebo"] }
  }
}

Install steps taken from the project README (its recommended path first). Placeholders are the maintainer's. Not bench-tested by HardwareMCP yet.