How deepak61296/mavlink-mcp works
mavlink-mcp exposes drone telemetry, camera imagery, and guarded flight actions as MCP tools for an LLM client. The main workflow is client request → server tool handling → telemetry-confirmed flight operation → live-state result; optional camera capture supports a fly–look–decide loop. The server resolves settings and selects a vehicle backend, while flight logic uses safety limits and shared geographic helpers. The pi extension is an alternate MCP client bridge. Source excerpts are partial, so unshown relationships are omitted.
Main entry points: server.py MCP server · flight.py Flight tools · ardupilot.py ArduPilot backend · interfaces.py Backend contract
Components 12
MCP entry
- MCP server
mavlink_mcp/server.py - pi bridge
integrations/pi/mavlink-mcp.ts
Flight operations
- Flight tools
mavlink_mcp/flight.py - Safety limits
mavlink_mcp/safety.py
Vehicle backends
- Backend selection
mavlink_mcp/backends/__init__.py - ArduPilot backend
mavlink_mcp/backends/ardupilot.py - In-memory backend
mavlink_mcp/backends/fake.py
Camera and geography
- Geographic helpers
mavlink_mcp/geo.py - Camera capture
mavlink_mcp/camera.py
Configuration and contracts
- Settings resolution
mavlink_mcp/config.py - Backend contract
mavlink_mcp/interfaces.py
Other components
- LLM / MCP client
Connections 18
- LLM / MCP client → MCP server: calls tools
README.md - pi bridge → MCP server: spawns over stdio
integrations/pi/mavlink-mcp.ts - MCP server → Settings resolution: loads settings
mavlink_mcp/server.py - MCP server → Flight tools: builds tools
mavlink_mcp/server.py - MCP server → Camera capture: creates frame source
mavlink_mcp/server.py - MCP server → Backend selection: selects backend
mavlink_mcp/server.py - MCP server → ArduPilot backend: supports live vehicle
README.md - MCP server → In-memory backend: supports fake mode
README.md - Flight tools → Safety limits: checks limits
mavlink_mcp/flight.py - Flight tools → Geographic helpers: uses calculations
mavlink_mcp/flight.py - Flight tools → Backend contract: uses backend types
mavlink_mcp/flight.py - ArduPilot backend → Backend contract: implements contract
mavlink_mcp/backends/ardupilot.py - In-memory backend → Backend contract: implements contract
mavlink_mcp/backends/fake.py - ArduPilot backend → Geographic helpers: uses calculations
mavlink_mcp/backends/ardupilot.py - In-memory backend → Geographic helpers: uses calculations
mavlink_mcp/backends/fake.py - Camera capture → Backend contract: uses result type
mavlink_mcp/camera.py - MCP server → ArduPilot backend: reads telemetry
mavlink_mcp/server.py - MCP server → Camera capture: captures images
README.md