Skip to main content
Glama

Server Details

Specs of FPV drone parts and every Betaflight/INAV CLI setting by release; checks a pasted diff

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
fpvdb/fpv-db-mcp
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct object and action: fw_check_cli validates a pasted config against one release, fw_diff compares two releases, fw_param looks up a single setting, search_parts queries a part type, and part_specs fetches one part by slug. The fw_* trio could superficially look similar but the input (paste vs. two releases vs. one setting name) makes selection unambiguous. The parts pair follows a clear search-then-fetch split.

Naming Consistency4/5

All names are snake_case with a consistent domain prefix (fw_* for firmware CLI, part(s)_* for hardware), which makes grouping obvious. The second token mixes verbs and nouns (check_cli, diff, param vs. specs, search), so it is not a strict verb_noun pattern throughout. Still highly readable and predictable once the two clusters are recognized.

Tool Count5/5

Five tools is well-scoped for a read-only reference database covering two domains. Each tool earns its place: validation, cross-release diffing, single-setting lookup, search, and detail fetch. There is no filler and no obvious need to split or merge anything.

Completeness3/5

Core workflows are covered, but there are notable gaps: no way to list available firmware releases/targets, no way to browse all settings for a release, and no cross-type or free-text part discovery (search_parts requires an explicit type; field lists only surface via an unknown-field error trick). Agents can often work around these, but a few discovery paths are dead ends.

Available Tools

5 tools
fw_check_cliCheck a Betaflight or INAV diffA
Read-only
Inspect

Checks a pasted diff all / dump against a release: every set line whose setting does not exist, was renamed or removed, or whose value is out of range or not in the value list, plus lines that only repeat the firmware default. The release of the paste is read from its # Betaflight / ... X.Y.Z or # INAV/<target> X.Y.Z header, which also picks the firmware when none is given. Other commands (aux, serial, resource) are counted, not checked.

Inputs: text (required), version, firmware.

fw_diffBetaflight / INAV settings diffA
Read-only
Inspect

What changed in the CLI settings between two releases: added, removed, renamed (only sourced renames) and changed (range, values, default) settings.

Inputs: from (required), to, firmware.

fw_paramBetaflight / INAV CLI settingA
Read-only
Inspect

One CLI setting of a firmware release: type, allowed range or values, firmware default (with no board config), the source line (settings.c or settings.yaml), and its history across releases (renames, range and default changes). Old names are followed through sourced renames.

Inputs: name (required), version, firmware.

part_specsFPV part spec sheetA
Read-only
Inspect

The full spec sheet of one part by its slug (the last segment of its fpv-db.com URL, e.g. iflight-xing2-2207 for /motors/iflight-xing2-2207/): specs, bench thrust table where measured, VTX table where published, the sources the specs were verified against, and caveats.

Inputs: slug (required), type.

search_partsSearch FPV partsA
Read-only
Inspect

Finds published parts of one type by spec. filters maps a spec field to a number (equals, or any element of a list), a string (case-insensitive substring) or {min, max} (numeric range). query matches brand and model. An unknown field returns the type's field list. Example: type=motor, filters={"stator": "2207", "weight_g": {"max": 33}}.

Inputs: type (required), limit, query, filters.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • 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
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to read and configure flight controllers running Betaflight firmware over USB serial using MSP, with tools for telemetry, battery monitoring, PID/rates tuning, filters, modes, and saving configuration.
      38
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables inspecting and comparing exported TunerStudio-style tune files and summarizing CSV logs, with firmware metadata, units, checksums, and format capabilities, without connecting to an ECU or modifying files.
      4
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.