[flovec]

I was looking into the MCP route too, and found some libraries abstracting mavlink for this use case (there’s at least one white paper documenting failure modes of LLMs trying to issue mavlink commands without an abstraction), but realized that autopilot like PX4 exists. My use case was more about autonomous flight, and it seemed better to just set waypoints and put some guards on other inputs. When paired with QGroundControl plans, all I needed to do for most flight paths was generate or update a .plan file using an LLM and other methodologies. I wasn’t super happy with the QGroundControl -> Gazebo rendering (no tie into real world terrain out of the box), but it did sort of work out of the box without too much effort!

[silksowed]

Interesting. I've been building around that MCP abstraction and have had some early success flying in Cosys-Airsim (and Gazebo before that): https://github.com/jakedcmp/droneserver . I am starting to realize I need to break apart the MCP interface from all the other pieces of the stack for cleaner architecture but thats pending work. My flow goes like this: LLM -> MCP tools -> droneserver -> MAVSDK/MAVLink -> PX4/Ardupilot -> Cosys-Airsim Software in the Loop testing. What is novel for me is not having to learn how to fly a drone and bringing that capability into already existing technologies like PX4 autopilot. I have been attempting to code my own mission planning so I will check out QGroundControl as that might already be a solved problem and not worth building from scratch. I have also built the foundation of video streaming back from the drone so I can run video/image perception. Once I get perception working I am hoping I can build intent level autonomy where images are analyzed according to high level mission plan and potentially re-task the drone based on that. For example, the user issues simple command to fly around the property and scan for broken parts of the fence. During flight if an image of a broken fence is perceived, then the drone stops its flight and goes closer to capture additional imaging/video and document a gps location. Still hacking things together towards a real demo so the code probably wont port over well but idk. To anyone in this thread who wants to discuss further or collaborate let me know, it seems we are all working in a similar domain but from slightly different angles. Exciting area to build, I know there is big demand for solutions in this space over the next decade.

[flovec]

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/ QGroundControl just like Gazebo does. Might be looking into that :)