FPV-DB MCP

An official Model Context Protocol server providing read-only access to FPV-DB's independent database of drone components and firmware data. It allows agents to retrieve detailed specifications for quads, motors, batteries, props, stacks, cameras, and VTXs, as well as query Betaflight and INAV firmware CLI settings, diffs, and compatibility checks.

Visit FPV-DB

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by FPV-DB

MCP endpoint (Streamable HTTP)

https://fpv-db.com/mcp

Vendor documentation

What you can do with it

Retrieve full specifications and source URLs for specific FPV drone components
Check differences between two firmware releases using fw_diff
Validate a pasted CLI diff against a specific firmware release
Search and filter components by technical specifications

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: com.fpv-db/fpv-db@1.0.0 Project website

Protocol and capabilities

Server: fpv-db 1.0.0
MCP protocol: 2025-06-18
Tools: 5 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Spec sheets of FPV drone parts (motors, quads, batteries, props, stacks, cameras, VTX) and the Betaflight and INAV CLI settings of each release (Betaflight from settings.c with defaults read off SITL builds, INAV from settings.yaml resolved by its own generator). Parts data CC BY 4.0, firmware data GPL-3.0; cite the page URL each result carries. Spec sheets only - no reviews or rankings.

Tools

5 advertised

fw_param — Betaflight / INAV CLI setting

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

fw_param input schema

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Setting name, as in `set <name> = ...`"
    },
    "version": {
      "type": "string",
      "description": "Release, e.g. 2026.6.2 or 4.5 (default: latest)"
    },
    "firmware": {
      "enum": [
        "betaflight",
        "inav"
      ],
      "type": "string",
      "default": "betaflight",
      "description": "Firmware (fw_check_cli: default is the one the paste's header names)"
    }
  },
  "additionalProperties": false
}

fw_param annotations

{
  "readOnlyHint": true,
  "openWorldHint": false
}

fw_diff — Betaflight / INAV settings diff

Advertised by the server during the last successful anonymous check.

Advertised read-only

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

fw_diff input schema

{
  "type": "object",
  "required": [
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Newer release (default: latest)"
    },
    "from": {
      "type": "string",
      "description": "Older release, e.g. 4.5"
    },
    "firmware": {
      "enum": [
        "betaflight",
        "inav"
      ],
      "type": "string",
      "default": "betaflight",
      "description": "Firmware (fw_check_cli: default is the one the paste's header names)"
    }
  },
  "additionalProperties": false
}

fw_diff annotations

{
  "readOnlyHint": true,
  "openWorldHint": false
}

fw_check_cli — Check a Betaflight or INAV diff

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

fw_check_cli input schema

{
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "The CLI text, up to 100 KB"
    },
    "version": {
      "type": "string",
      "description": "Release to check against (default: latest)"
    },
    "firmware": {
      "enum": [
        "betaflight",
        "inav"
      ],
      "type": "string",
      "default": "betaflight",
      "description": "Firmware (fw_check_cli: default is the one the paste's header names)"
    }
  },
  "additionalProperties": false
}

fw_check_cli annotations

{
  "readOnlyHint": true,
  "openWorldHint": false
}

part_specs — FPV part spec sheet

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

part_specs input schema

{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    },
    "type": {
      "enum": [
        "motor",
        "quad",
        "battery",
        "prop",
        "stack",
        "camera",
        "vtx"
      ],
      "type": "string",
      "description": "Part type, if known"
    }
  },
  "additionalProperties": false
}

part_specs annotations

{
  "readOnlyHint": true,
  "openWorldHint": false
}

search_parts — Search FPV parts

Advertised by the server during the last successful anonymous check.

Advertised read-only

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

search_parts input schema

{
  "type": "object",
  "required": [
    "type"
  ],
  "properties": {
    "type": {
      "enum": [
        "motor",
        "quad",
        "battery",
        "prop",
        "stack",
        "camera",
        "vtx"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Words that must appear in brand + model"
    },
    "filters": {
      "type": "object",
      "additionalProperties": true
    }
  },
  "additionalProperties": false
}

search_parts annotations

{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 385 ms
95th percentile latency: 385 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 7:35 AM UTC · probe · passed · 385 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http fpv-db-mcp https://fpv-db.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add fpv-db-mcp --url https://fpv-db.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable fpv-db-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start fpv-db-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http fpv-db-mcp https://fpv-db.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "fpv-db-mcp": {
      "serverUrl": "https://fpv-db.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like FPV-DB MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 6,643

Do you run FPV-DB MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing

FPV-DB MCP

Endpoint and access

What you can do with it

Source and maintenance

Protocol and capabilities

Server-provided instructions

Tools

Prompts

Resources

30-day availability

Maintenance history

Connect from your client

Claude Code

Codex

Cursor

Cline

VS Code

Gemini CLI

Claude Desktop

Windsurf

Let your agent find its tools

Other developer tools servers

Do you run FPV-DB MCP?