HackerPapers

arXiv:2601.15486cs.RO

An LLM-Agnostic, MAVLink-Based Drone Command and Control Interface and Agentic Harness Using the Model Context Protocol

Javier Noé Ramos Silva, Peter J. Burke

Early discovery. Linked by one identifiable commenter. This paper is outside the main ranking; a mention is not an endorsement.

Abstract

Artificial intelligence integrated with drone command and control (physical AI) offers a route to autonomy through large language models (LLMs), yet a unified LLM-to-drone interface has been missing. We present an LLM-agnostic command-and-control interface and agentic harness joining the Model Context Protocol (MCP) to MAVLink, the near-universal drone command-and-telemetry standard: "DroneServer" gives any MCP-capable LLM command, telemetry, mission, and safety functions over ArduPilot and PX4. Its 98 tools cover 223 of 238 client-side methods of MavSDK, MAVLink's library; 61 of the 98 were exercised in software-in-the-loop. We treat the LLM as an untrusted commander: zero public ports (externally verified); every command validated server-side (tiers, confirmation handshakes, independent geofence, audit log), exercised by an adversarial safety suite. Server-side mission state resolves the "fire-and-forget" mismatch: a scripted client's 37.8-minute mission survived a 4-minute disconnection. Over 1,000 simulated flights ran a ten-mission LLM-UAV control benchmark; eight of eleven models complete 90.0-100% of its six flying missions, and no aircraft left the permitted zone in 110 geofence-violation trials. On real hardware, the unmodified server commanded three quadcopters, GPS-guided and GPS-denied; five providers' models flew an unseen mission, ten of ten. The tests and datasets include: repeated trials, standardized evaluation tasks, success/failure statistics, latency analysis, uncertainty treatment, comparative benchmarking across models/platforms, prompt sets, mission complexity, tool-call traces, safety-intervention logs, and safety-performance assessment. The architecture is a scaffold for a higher-level drone-LLM operating system where plain-language commands realize complex missions, and a path to agent swarms commanding drone swarms under one security umbrella.

arXiv comments
Revised version. 67 pages, 15 figures, 2 tables, 70 references. Supplementary Information (88 pages, Notes S1-S17, 15 figures, 17 tables) attached as an ancillary file. Code: https://github.com/PeterJBurke/droneserver (v2.0.2, doi:10.5281/zenodo.22309419). Data: doi:10.5281/zenodo.22310050
Journal reference
DOI
Subjects
cs.RORobotics

On Hacker News

Linked by 1 identifiable commenter in 1 comment across 1 thread, from Apr 2026 to Apr 2026.

Comments linking this paper, per year.

Discussed in comments1 thread

  1. Fly Drones from the Browser 1 comment
    • droneserver was indeed the abstraction mentioned in https://arxiv.org/pdf/2601.15486 . The video/image perception is why I started looking into this domain in the first place, but I haven't gotten there yet. I hadn't seen Cosys-Airsim! I bet it could work in tandem w/…

      flovecView on HNParent context

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.