mavforge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAVFORGE_CONNECTION | No | The vehicle connection string, e.g. tcp:127.0.0.1:5760 or /dev/ttyACM0. Can be used instead of passing -c/--connection to the MCP server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mavforge_capabilitiesA | List MAVForge operations with their required permission, whether they modify the vehicle, and whether they are available or only planned. Does not contact the vehicle. |
| vehicle_infoA | Identify the connected vehicle: autopilot, vehicle type, firmware version and git hash, board IDs, MAVLink capabilities, whether it is a simulator (SITL), and any other vehicles heard on the link. Read-only. |
| vehicle_statusA | Snapshot of arming state, flight mode, system state, sensor presence/health,
whether the firmware's pre-arm checks are enabled (false = switched off on the
vehicle) and passing, battery, GPS fix, and STATUSTEXT messages
received since the server connected. Read-only; requests single messages
without changing stream rates. |
| params_listA | Download all parameters and return those matching an optional
case-insensitive glob (e.g. 'COMPASS_*'). Read-only. Takes a few seconds on
slow links. |
| params_getA | Read one parameter by exact name (1-16 letters, digits, underscores).
Read-only. Fails with |
| diagnoseA | Diagnose configuration and readiness problems. Read-only: gathers sensor
health, asks the firmware to run (not change) its pre-arm checks, downloads all
parameters and applies platform rules. Each finding has a |
| calibration_proceduresA | Explain every calibration MAVForge supports: preconditions, the physical steps the person at the vehicle must do, parameters it changes, how success is verified, and how cancellation behaves. Includes support for the connected vehicle when one is configured. Read-only. |
| params_backupA | Download every parameter and save it, together with the vehicle's identity and
firmware version, as a new backup file in MAVForge's backup directory on the
host. Does not change the vehicle; never overwrites an existing file. Returns a
|
| params_backupsA | List saved parameter backups (id, time, vehicle, firmware, completeness). Does not contact the vehicle. |
| params_diffA | Compare parameters with a saved backup ( |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target clearly distinct resources or actions, but several tools download all parameters (params_list, params_backup, diagnose) for different purposes, which could invite initial confusion. Descriptions mostly resolve this, and vehicle_info vs vehicle_status and calibration_procedures vs diagnose are separable.
All names use snake_case and are grouped with readable prefixes (params_, vehicle_), but the set is not a strict verb_noun pattern. Minor inconsistencies like params_backup vs params_backups and standalone names such as diagnose and calibration_procedures keep it from a perfect score.
Ten tools is well scoped for a vehicle diagnostics and parameter-management server. Capabilities, vehicle identity/status, parameter read/backup/list/diff, diagnosis, and calibration documentation each have a clear role.
The surface covers read-only inspection, diagnosis, backup, and diffing well, but it has notable dead ends for configuration work: no parameter write/apply, no backup restore, and no tool to execute the calibration procedures it documents. This is a significant gap if the server is intended to support MAVForge configuration workflows rather than only diagnostics.