FPV-DB

com.fpv-dbPublished by fpv-db.comOfficial publisherv1.0.0Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote MCP server for FPV drone part spec sheets and Betaflight/INAV CLI settings by firmware release, including checks of pasted CLI diffs.

What you can do
  • Look up one firmware CLI setting: type, allowed range or values, default, source line and history across releases
  • Compare two firmware releases to see added, removed, renamed and changed CLI settings
  • Check a pasted diff all or dump against a release for unknown, renamed, removed or out-of-range settings and lines that only repeat defaults
  • Search published parts of one type by spec filters or by brand and model query
  • Read a full part spec sheet by slug, with bench thrust or VTX tables, verification sources and caveats
When to use it
Useful when tuning or migrating Betaflight or INAV configurations and you need to know whether a CLI setting exists, changed or is in range for a given release, or when comparing FPV parts such as motors, batteries, props, stacks, cameras and VTX by their published specs.
Requirements
A remote streamable HTTP endpoint at fpv-db.com; no packages, environment variables, headers or authentication are declared.
Before you install
Results are spec sheets only, with no reviews or rankings. Parts data is CC BY 4.0 and firmware data GPL-3.0, and the server asks that the page URL carried by each result be cited. Pasted CLI text is sent to the remote service.

Installation

In SourceWeft

  1. Open FPV-DB in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.fpv-db%2Ffpv-db/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fpv-db": {
      "type": "http",
      "url": "https://fpv-db.com/mcp"
    }
  }
}

Tools

5

fw_param

Betaflight / INAV CLI setting

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.

Parametersnamerequiredversionfirmware

fw_diff

Betaflight / INAV settings diff

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

Parameterstofromrequiredfirmware

fw_check_cli

Check a Betaflight or INAV diff

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.

Parameterstextrequiredversionfirmware

part_specs

FPV part spec sheet

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.

Parametersslugrequiredtype

search_parts

Search FPV parts

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}}.

Parameterstyperequiredlimitqueryfilters

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.