Skip to main content
Glama
Betaflight MCP Server

Betaflight MCP Server

by AlanOgic

Betaflight MCP Server

A Model Context Protocol server that exposes 38 tools to read and configure a Betaflight flight controller over USB serial using the MSP protocol.

MCP is not Claude-specific. Any MCP-compatible client works: Claude Desktop, Cursor, Cline, Continue, custom LLM agents, Alexa skills, or any application using the MCP SDK.


How it works

┌────────────────────────┐    MCP (stdio or SSE)    ┌──────────────────────────┐
│    Any MCP Client      │ ◄──────────────────────► │  betaflight-mcp server   │
│  Claude / Cursor / ... │                           │  Python · FastMCP        │
└────────────────────────┘                           └──────────┬───────────────┘
                                                                │  MSP protocol
                                                                │  pyserial · USB
                                                     ┌──────────▼───────────────┐
                                                     │   Flight Controller      │
                                                     │   Betaflight 4.x         │
                                                     └──────────────────────────┘

The server translates MCP tool calls into MSP (MultiWii Serial Protocol) frames, sends them to the FC over USB serial, parses the binary response and returns structured JSON.


Related MCP server: iNAV MCP Server

Prerequisites

Requirement

Version

Notes

Python

≥ 3.10

3.12+ recommended

Betaflight firmware

≥ 4.0 (API ≥ 1.40)

On any F4/F7/H7 FC

USB cable

—

FC connected to host machine


Installation

git clone https://github.com/your-username/betaflight-mcp.git
cd betaflight-mcp

python -m venv .venv

# Linux / macOS
source .venv/bin/activate

# Windows
.venv\Scripts\activate

pip install -r requirements.txt

Linux — serial port permissions (one-time setup):

sudo usermod -aG dialout $USER
# then log out and back in

Configuration

All settings are controlled via environment variables — no config file to edit.

Variable

Default

Description

BETAFLIGHT_PORT

auto-detect

Serial port of the FC. Unset: connect picks the single Betaflight FC plugged in over USB (USB product string Betaflight…, or STM32/AT32/APM32 VCP VID:5740)

BETAFLIGHT_BAUD

115200

Baud rate (must match Betaflight config)

BETAFLIGHT_TIMEOUT

2.0

Serial read timeout in seconds

BETAFLIGHT_MAX_SAMPLING_S

60.0

Maximum duration_s accepted by the RC sampling tools (they block the server while sampling)

BETAFLIGHT_EEPROM_TIMEOUT

5.0

Read timeout for the save_config acknowledgement (the FC blocks while writing flash)

Set them inline or in your shell:

# inline
BETAFLIGHT_PORT=/dev/ttyACM0 python main.py

# or export
export BETAFLIGHT_PORT=/dev/ttyACM0
export BETAFLIGHT_BAUD=115200
python main.py

Find your FC's serial port

# Linux
ls /dev/ttyUSB* /dev/ttyACM*

# macOS
ls /dev/tty.usbmodem* /dev/tty.usbserial*

# Windows — PowerShell
[System.IO.Ports.SerialPort]::getportnames()

# Or use the built-in tool (any platform):
python -c "
from server.tools import tool_list_serial_ports
import json; print(json.dumps(tool_list_serial_ports(), indent=2))
"

Important: close Betaflight Configurator before starting the MCP server. Both cannot hold the serial port open at the same time.


Client setup

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "betaflight": {
      "command": "/absolute/path/to/.venv/bin/python",
      "args": ["/absolute/path/to/betaflight-mcp/main.py"],
      "env": {
        "BETAFLIGHT_PORT": "/dev/ttyACM0",
        "BETAFLIGHT_BAUD": "115200"
      }
    }
  }
}

Restart Claude Desktop. The 38 tools appear automatically in the tool picker.

Claude Code (CLI)

claude mcp add -s user \
  -e BETAFLIGHT_PORT=/dev/ttyACM0 \
  -e BETAFLIGHT_BAUD=115200 \
  -- betaflight \
  /absolute/path/to/.venv/bin/python \
  /absolute/path/to/betaflight-mcp/main.py

Note : le -- doit être placé avant le nom (betaflight), pas après. Sans lui, le parser variadique de -e consomme les arguments suivants.

Scopes disponibles : local (projet courant), project (.mcp.json versionné), user (global, tous les projets). Vérifier avec claude mcp list.

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "betaflight": {
      "command": "/absolute/path/to/.venv/bin/python",
      "args": ["/absolute/path/to/betaflight-mcp/main.py"],
      "env": {
        "BETAFLIGHT_PORT": "/dev/ttyACM0"
      }
    }
  }
}

Cline / Continue (VS Code)

Same JSON format as above, placed in the respective extension's MCP server config.

Custom agent (HTTP transport)

For any client that talks to an HTTP endpoint instead of launching a subprocess. FastMCP's run() only takes the transport; host and port are server settings (also readable from FASTMCP_HOST / FASTMCP_PORT):

python -c "
from main import app
app.settings.host = '127.0.0.1'
app.settings.port = 8000
app.run(transport='streamable-http')
"

Then point your client at http://127.0.0.1:8000/mcp. For legacy SSE clients use transport='sse' and http://127.0.0.1:8000/sse. The server has no authentication, so keep it on 127.0.0.1 or a trusted network.

MCP SDK (Python / TypeScript)

from mcp import ClientSession, StdioServerParameters
from mcp.client.stdio import stdio_client

server_params = StdioServerParameters(
    command="python",
    args=["/path/to/betaflight-mcp/main.py"],
    env={"BETAFLIGHT_PORT": "/dev/ttyACM0"},
)

async with stdio_client(server_params) as (read, write):
    async with ClientSession(read, write) as session:
        await session.initialize()
        result = await session.call_tool("connect", {"port": "/dev/ttyACM0"})
        result = await session.call_tool("get_fc_status", {})

Available tools

All read operations are safe at any time. Write operations (set_*) require calling save_config afterwards to persist changes to EEPROM.

Connection

Tool

Parameters

Description

list_serial_ports

—

List all serial ports on the host

connect

port, baudrate

Open serial connection to the FC

disconnect

—

Close the connection

FC identity

Tool

MSP

Description

get_board_info

BOARD_INFO · FC_VARIANT · FC_VERSION · API_VERSION

Firmware variant (BTFL), version, target name, MCU type

Telemetry

Tool

MSP

Description

get_fc_status

STATUS_EX (150)

Cycle time, CPU load, arming flags, profiles

get_imu_data

RAW_IMU (102)

Accelerometer (g), gyroscope (°/s), magnetometer

get_attitude

ATTITUDE (108)

Roll / pitch / yaw in degrees

get_altitude

ALTITUDE (109)

Altitude (m) and variometer (cm/s)

get_rc

RC (105)

All RC channel values (µs)

get_motors

MOTOR (104)

Motor outputs (µs)

Battery

Tool

MSP

Description

get_battery

ANALOG (110)

Voltage (V), current (A), mAh drawn, RSSI

get_battery_state

BATTERY_STATE (130)

Cell count, capacity, state (OK / WARNING / CRITICAL)

get_voltage_meters

VOLTAGE_METERS (128)

All voltage meters

get_battery_config

BATTERY_CONFIG (32)

—

set_battery_config

SET_BATTERY_CONFIG (33)

settings (CLI name → value)

get_profiles

STATUS_EX + BATTERY_PROFILE (0x300E)

—

select_profile

SELECT_SETTING (210)

kind (pid/rate/battery), index

get_battery_profiles

BATTERY_PROFILE (0x300E)

—

set_battery_profile

SET_BATTERY_PROFILE (0x300F)

index, settings

get_current_meters

CURRENT_METERS (129)

All current meters

PID tuning

Tool

MSP

Parameters

Description

get_pid_values

PID (112)

—

P/I/D per axis (roll, pitch, yaw, level, mag)

set_pid_values

SET_PID (202)

axis, p, i, d

Write P/I/D for one axis (0–250); other axes are preserved

get_rates

RC_TUNING (111)

—

Per-axis rates in the configurator units of the active rates type (Betaflight, Raceflight, KISS, Actual, Quick), full-stick max °/s, throttle curve

set_rates

SET_RC_TUNING (204)

{roll,pitch,yaw}_{rc_rate,rate,expo}, throttle_mid, throttle_expo

Per-axis update in the active rates type's units, checked against firmware limits; returns read-back values

get_pid_advanced

PID_ADVANCED (94) + SIMPLIFIED_TUNING (140)

—

Advanced PID settings of the active profile, keyed by CLI name (feedforward, D-max — D-min before 2025.12 —, iterm relax, anti-gravity, TPA, simplified PID mode)

set_pid_advanced

SET_PID_ADVANCED (95) + SET_SIMPLIFIED_TUNING (141)

settings (CLI name → value)

Write only the given advanced settings; Betaflight 2025.12+ only; returns read-back values

Configuration

Tool

MSP

Description

get_modes

MODE_RANGES (34)

AUX switch assignments (box_id, channel, µs range)

get_feature_config

FEATURE_CONFIG (36)

Enabled features (AIRMODE, GPS, LED_STRIP…)

get_advanced_config

ADVANCED_CONFIG (90)

ESC protocol (DSHOT), gyro/PID denominators, PWM rate

get_filter_config

FILTER_CONFIG (92)

—

set_filter_config

SET_FILTER_CONFIG (93)

settings (CLI name → value)

get_sensor_config

SENSOR_CONFIG (96)

Accelerometer, barometer, magnetometer hardware

System

Tool

MSP

Description

save_config

EEPROM_WRITE (250)

Persist current config to EEPROM — always call after set_*

reboot_fc

SET_REBOOT (68)

Reboot the flight controller


Testing

Unit tests (no FC required)

python -m pytest tests/test_msp.py -v
# 34 tests — MSP v1/v2 framing, CRC, all response parsers

Interactive inspector (no FC required)

pip install "mcp[cli]"   # one-time
mcp dev main.py
# opens http://localhost:5173 — call any tool from the browser

End-to-end with a real FC

# Quick smoke test
BETAFLIGHT_PORT=/dev/ttyACM0 python3 - <<'EOF'
import json
from server.tools import tool_connect, tool_get_fc_status, tool_get_battery, tool_disconnect

print(json.dumps(tool_connect("/dev/ttyACM0"), indent=2))
print(json.dumps(tool_get_fc_status(), indent=2))
print(json.dumps(tool_get_battery(), indent=2))
tool_disconnect()
EOF

Project structure

betaflight-mcp/
├── main.py                      # Entry point — FastMCP app, tool registration
├── requirements.txt
├── pyproject.toml
│
├── betaflight/
│   ├── msp_codes.py             # All MSP command codes (v1 + v2)
│   ├── msp.py                   # MSP v1 / v2 framing, CRC8/DVB-S2, serial I/O
│   ├── commands.py              # Response parsers (DataReader), all 25+ commands
│   ├── rates.py                 # Rates types: units, firmware limits, max °/s
│   ├── msp_fields.py            # Table-driven MSP payload fields (read / validate / patch)
│   ├── pid_advanced.py          # MSP_PID_ADVANCED field table (CLI names)
│   ├── filter_config.py         # MSP_FILTER_CONFIG field table (CLI names)
│   ├── battery_config.py        # MSP_BATTERY_CONFIG field table (CLI names)
│   ├── battery_profiles.py      # MSP2 battery profiles (Betaflight 2026.6+)
│   └── serial_conn.py           # pyserial wrapper
│
├── server/
│   ├── tools.py                 # MCP tool functions (typed schemas) + MCP_TOOLS registry
│   └── validators.py            # Pre-write checks (PID, rates)
│
├── config/
│   └── settings.py              # Env-var based configuration
│
├── tests/
│   └── test_msp.py              # 34 unit tests (mock serial)
│
└── examples/
    └── claude_desktop_config.json

Safety

⚠ Never arm the FC via MCP with propellers attached.

  • Writes are refused while the FC is armed. Before set_pid_values, set_rates, save_config and reboot_fc, the server reads MSP_STATUS_EX in the same serial transaction and aborts if the ARM flag is set, or if the arming state can't be read (fail-closed)

  • A write reports success: true only when the FC acknowledges it; otherwise the tool returns an error and the value should be read back before retrying

  • All set_* operations are not automatically saved — always call save_config to persist

  • set_motor sends raw PWM values directly to ESCs — only use with props off and FC in motor-test mode

  • The server has no authentication — only expose the HTTP transports on trusted networks


Troubleshooting

SerialException: [Errno 16] Device or resource busy → Close Betaflight Configurator (or any other app using the port).

SerialException: [Errno 2] No such file or directory → Wrong port. Run list_serial_ports or ls /dev/ttyUSB* /dev/ttyACM* to find the correct one.

connect succeeds but all get_* return None → Check baudrate. Betaflight default is 115200. Verify in Betaflight Configurator → Ports tab → USB VCP.

Timeout on read (BETAFLIGHT_TIMEOUT=2.0) → Increase timeout: BETAFLIGHT_TIMEOUT=5.0. Can happen on busy systems or slow FCs.

Permission denied on Linux → sudo usermod -aG dialout $USER, then log out and back in.

connect fails with "Aucune réponse MSP" → The port opened but nothing answered MSP_API_VERSION: wrong device, FC still booting, or wrong baudrate. Some FCs need a battery for a full boot. connect closes the port again, so nothing is left half-open.

connect fails with "Firmware … non supporté" or "API MSP … trop ancienne" → Only Betaflight (BTFL) with MSP API ≥ 1.40 is supported. INAV and other MSP firmwares use different payload layouts, so the server refuses to talk to them.

connect says the port is busy right after a reboot → Something reopened the port as soon as the FC came back. Often it's the web Betaflight Configurator (app.betaflight.com, Web Serial) left open in a browser tab with auto-connect. Disconnect it there, or close the tab.

A 1S HV pack is detected as 2S (low-battery alarms, wrong PID profile) → Betaflight counts cells as floor(voltage / vbat_max_cell_voltage) + 1. With the default 4.30 V max, a charged HV cell (4.35 V) counts as 2S. Set vbat_max_cell_voltage to 440 on every battery profile (set_battery_profile), since on 2026.6 the voltages belong to the active battery profile.

Current reads tens of amps with the motors stopped → The board has no current sensor but current_meter is ADC (the default after a reflash). Run set_battery_config({"current_meter": "NONE"}), then save_config and reboot_fc.

Tools fail with "Non connecté" after reboot_fc → Expected: the USB port disappears during the reboot, so the server closes the connection. Wait a few seconds and call connect again.


License

MIT — see LICENSE.

Available Tools

38 tools
connectA
Idempotent

Connecte le serveur au FC via port série (ferme la connexion précédente). Vérifie l'identité : réponse MSP, firmware Betaflight (BTFL), API >= 1.40 ; sinon échec et port refermé. Retourne api_version, fc_variant, fc_version.

Inputs: port, baudrate.

detect_rc_channel_moveA
Read-only

Mode guidé (une étape) : poll les canaux RC pendant duration_s secondes et retourne le canal dont le pic de delta depuis la baseline est le plus grand. Protocole : (1) get_rc pour obtenir la baseline au repos, (2) demander à l'utilisateur de bouger UN SEUL contrôle, (3) appeler cet outil — répéter pour chaque axe (roll, pitch, yaw, throttle). Plus fiable qu'un snapshot instantané car capture le pic sur toute la fenêtre.

Inputs: baseline (required), threshold, duration_s.

detect_rc_mappingA
Read-only

Mode passif : échantillonne tous les canaux RC pendant N secondes (~50 Hz) et classifie chacun — throttle (repos ~1000 µs), stick (centré ~1500 µs, grand débattement), switch_2pos, switch_3pos, unused. Identifie la convention TAER (throttle=ch0) ou AETR (throttle=ch2). roll/pitch/yaw restent ambigus : combiner avec detect_rc_channel_move. Demander à l'utilisateur de bouger tous les sticks et switches pendant la mesure.

Inputs: duration_s.

disconnectA
Idempotent

Ferme la connexion série vers le FC (après la requête MSP en cours)

Inputs: no named parameters.

get_advanced_configC
Read-only

Config avancée : dénominateurs gyro/PID, protocole ESC (DSHOT), PWM rate

Inputs: no named parameters.

get_altitudeA
Read-only

Altitude (m) et variomètre (cm/s) depuis le baromètre

Inputs: no named parameters.

get_attitudeA
Read-only

Attitude du drone : roulis, tangage, cap en degrés

Inputs: no named parameters.

get_batteryC
Read-only

Tension batterie (V), courant (A), mAh consommés, RSSI

Inputs: no named parameters.

get_battery_configB
Read-only

Config batterie, noms CLI : vbat_min/warning/max_cell_voltage (0.01 V), bat_capacity (mAh), battery_meter et current_meter (source de mesure)

Inputs: no named parameters.

get_battery_profilesA
Read-only

Les 3 profils batterie (Betaflight 2026.6+) : tensions cellule min/warning/full/max (0.01 V), capacité, force_battery_cell_count, cbat_alert_percent. Le nombre de cellules détecté vaut floor(tension / vbat_max_cell_voltage) + 1.

Inputs: no named parameters.

get_battery_stateA
Read-only

État détaillé de la batterie : cellules, capacité, état (OK/WARNING/CRITICAL)

Inputs: no named parameters.

get_board_infoA
Read-only

Retourne l'identité du FC : variante firmware (BTFL), version, carte, MCU, version API

Inputs: no named parameters.

get_current_metersB
Read-only

Liste tous les ampèremètres disponibles sur le FC

Inputs: no named parameters.

get_fc_statusA
Read-only

État général du FC : cycle time, capteurs actifs, flags arming, charge CPU

Inputs: no named parameters.

get_feature_configB
Read-only

Features Betaflight activées (AIRMODE, LED_STRIP, GPS, etc.)

Inputs: no named parameters.

get_filter_configB
Read-only

Configuration des filtres, noms CLI : lowpass gyro/D-term statiques et dynamiques (types PT1/BIQUAD/PT2/PT3), notches, dyn notch, filtre RPM, yaw_lowpass_hz

Inputs: no named parameters.

get_imu_dataB
Read-only

Données IMU : accéléromètre (g), gyroscope (°/s), magnétomètre

Inputs: no named parameters.

get_modesB
Read-only

Plages de modes RC actifs (AUX switches) : box_id, canal, min/max µs

Inputs: no named parameters.

get_motorsB
Read-only

Sorties moteurs actuelles (µs). 0 = moteur inactif

Inputs: no named parameters.

get_pid_advancedB
Read-only

Réglages PID avancés du profil actif, noms CLI : feedforward (f_roll/f_pitch/f_yaw, feedforward_*), D-max (d_max_* ; d_min_* avant Betaflight 2025.12), iterm relax, anti-gravity, acc_limit, angle_limit, TPA, throttle_boost, simplified_pids_mode

Inputs: no named parameters.

get_pid_valuesB
Read-only

Valeurs PID (P/I/D) pour chaque axe : roll, pitch, yaw, level, mag

Inputs: no named parameters.

get_profilesB
Read-only

Profils actifs : pid_profile (et pid_profile_count), rate_profile, battery_profile (Betaflight 2026.6+)

Inputs: no named parameters.

get_ratesA
Read-only

Rates RC par axe (roll, pitch, yaw) dans les unités du configurateur pour le rates_type actif (BETAFLIGHT, RACEFLIGHT, KISS, ACTUAL, QUICK) : rc_rate, rate, expo, libellés (labels), rate_limit_dps et max_rate_dps (vitesse à plein manche). Throttle mid/expo/limit/hover.

Inputs: no named parameters.

get_rcA
Read-only

Valeurs actuelles des canaux RC (µs, typiquement 1000-2000)

Inputs: no named parameters.

get_sensor_configB
Read-only

Configuration des capteurs : accéléromètre, baromètre, magnétomètre

Inputs: no named parameters.

get_voltage_metersB
Read-only

Liste tous les voltmètres disponibles sur le FC

Inputs: no named parameters.

list_serial_portsB
Read-only

Liste les ports série ; is_betaflight signale les FC Betaflight détectés (USB)

Inputs: no named parameters.

measure_rc_noiseA
Read-only

Poll les canaux RC pendant N secondes (~50 Hz) et retourne le bruit mesuré (95e percentile de déviation) ainsi qu'une valeur de deadband suggérée par canal. À utiliser sticks au repos.

Inputs: channels, duration_s.

reboot_fcA
Destructive

Redémarre le FC (refusé si armé). La connexion est fermée : rappeler connect après quelques secondes.

Inputs: no named parameters.

save_configA
DestructiveIdempotent

Sauvegarde la configuration courante en EEPROM du FC (obligatoire après tout SET)

Inputs: no named parameters.

select_profileA
DestructiveIdempotent

Active un profil PID, de rates ou batterie (2026.6+). Vérifié par relecture : le firmware ignore un index hors plage. Refusé si FC armé. Le choix n'est gardé au redémarrage qu'après save_config. Note : le firmware change seul de profil PID au branchement de la batterie selon auto_profile_cell_count (voir get_pid_advanced).

Inputs: kind (required), index (required).

set_battery_configA
DestructiveIdempotent

Modifie la config batterie (noms CLI, voir get_battery_config). Tensions en 0.01 V, ordre min <= warning <= max obligatoire. current_meter=NONE si le FC n'a pas de capteur de courant. Changer une source de mesure exige save_config puis reboot_fc (reboot_required dans la réponse). Betaflight 2025.12+. Refusé si FC armé.

Inputs: settings (required).

set_battery_profileA
DestructiveIdempotent

Modifie un profil batterie par index (Betaflight 2026.6+), actif ou non. Seuls les champs fournis changent ; ordre min <= warning <= full <= max obligatoire. Refusé si FC armé. Appeler save_config ensuite.

Inputs: index (required), settings (required).

set_filter_configA
DestructiveIdempotent

Modifie des filtres (noms CLI, voir get_filter_config). Seuls les champs fournis changent. Filtres gyro globaux ; D-term et yaw_lowpass_hz du profil PID actif. Le firmware peut corriger des valeurs incohérentes : la réponse contient les valeurs relues. Betaflight 2025.12+ (API >= 1.47). Refusé si FC armé. Appeler save_config ensuite.

Inputs: settings (required).

set_pid_advancedA
DestructiveIdempotent

Modifie des réglages PID avancés du profil actif (noms CLI, voir get_pid_advanced). Seuls les champs fournis changent. simplified_pids_mode=OFF empêche le firmware de recalculer les PIDs depuis les curseurs (ex. au prochain batch CLI). Betaflight 2025.12+ (API >= 1.47) uniquement. Refusé si FC armé. Retourne les valeurs relues. Appeler save_config ensuite.

Inputs: settings (required).

set_pid_valuesA
DestructiveIdempotent

Modifie les valeurs PID pour un axe (roll, pitch, yaw, level, mag). Les autres axes sont conservés. Appeler save_config ensuite.

Inputs: d (required), i (required), p (required), axis (required).

set_ratesA
DestructiveIdempotent

Modifie les rates par axe. Seuls les paramètres fournis changent. Les valeurs sont dans les unités du rates_type ACTUEL du FC (appeler get_rates d'abord : ex. ACTUAL → rc_rate = Center Sensitivity en °/s, rate = Max Rate en °/s, expo 0-1 ; BETAFLIGHT → rc_rate 0-2.55, rate = super rate 0-1, expo 0-1). Retourne les valeurs relues et max_rate_dps. Appeler save_config ensuite.

Inputs: yaw_expo, yaw_rate, roll_expo, roll_rate, +7 more.

snapshot_rc_deltaA
Read-only

Compare un snapshot RC courant à une baseline. Retourne les canaux dont le delta dépasse le seuil (défaut 200 µs). Utiliser pour détecter quel canal bouge quand l'utilisateur déplace un stick ou active un interrupteur.

Inputs: baseline (required), threshold.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action purposes (get_/set_ pairs for PID, rates, filters, battery). However, the RC-detection cluster (snapshot_rc_delta, measure_rc_noise, detect_rc_mapping, detect_rc_channel_move) has overlapping sampling purposes, and the battery surface (get_battery, get_battery_state, get_voltage_meters, get_current_meters) requires reading descriptions carefully to distinguish.

    Naming Consistency4/5

    Strong verb_noun convention throughout (get_*, set_*, get_battery_config/set_battery_config, list_serial_ports, save_config, reboot_fc). Minor deviations: connect/disconnect are bare verbs, and select_profile/measure_rc_noise/add consistent enough to stay readable.

    Tool Count2/5

    38 tools is heavy and exceeds the comfortable 3-15 range. While the FC-config domain is genuinely broad, several read-only getters (get_voltage_meters, get_current_meters, get_sensor_config) could be consolidated, pushing this toward over-scoped.

    Completeness4/5

    Core lifecycle is well covered with matched get/set pairs for PID, filters, rates, battery, profiles, plus connection management and RC discovery. Gaps remain: get_advanced_config, get_feature_config, get_modes, and get_sensor_config have no corresponding setters, leaving write paths for those areas missing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with an ArduPilot vehicle in real-time via MAVLink, including reading state, inspecting and changing parameters, switching flight modes, diagnosing arming failures, and gated arming/disarming.
      58 PyPI
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to control Betaflight flight controllers over serial via MSP and CLI, providing real-time sensor reads, full CLI access, and auto-generated variable tools for configuration and tuning.
      100
      26 npm
      3
      AGPL 3.0