Skip to main content
Glama
msmith626

mavforge-mcp

by msmith626
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mavforge-mcp

No user-submitted related servers found.

    Related Servers

    • ardupilot-mavlink-mcp

      rmeadomavic
      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.
      29 PyPI
      4
      MIT

    • mavlink-mcp

      hieutachi
      A
      license
      A
      quality
      C
      maintenance
      Connects AI agents to MAVLink drones (PX4, ArduPilot) via a capability layer with safety guardrails, enabling telemetry, flight control, and mission management through natural language.
      12
      2
      MIT

    • Betaflight MCP

      bvandevliet
      A
      license
      B
      quality
      C
      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
      3 npm
      3
      AGPL 3.0

    • mcu-debug-mcp

      stillsurge
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to directly inspect and debug embedded hardware: reading/writing serial ports and bus devices, auto-detecting baud rates, parsing Modbus/NMEA/custom binary frames, plus diagnosing failures through a 45-rule fault-pattern library, error-code tables, and compile/flash error translation. Also provides pin-conflict checking, register and Cortex-M fault decoding, pre-validated driver and component selection libraries, board knowledge, and guarded flashing with post-flash byte-level verification.
      59
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources