English Français العربية

OpenDeviceDB

Official registry Other

Check 21,000+ devices with open firmware or protocols before reverse engineering one.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @opendevicedb/mcp
Claude Code 
claude mcp add opendevicedb -- npx -y @opendevicedb/mcp@0.3.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "opendevicedb": {
            "command": "npx",
            "args": [
                "-y",
                "@opendevicedb/mcp@0.3.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

OpenDeviceDB

English | 简体中文

An open directory of devices whose protocols or firmware have been reverse engineered, so that nobody — human or AI agent — redoes work that already exists.

  • Humans: browse the directory, device pages and news on the website (site/).
  • Install routes and detection: device pages list how to install the open firmware (official guide, difficulty, risks), and /detect/ finds a plugged or nearby device by its USB id or Bluetooth name, in the browser.
  • Agents: query it through the MCP server (packages/mcp) before starting a reverse-engineering job, claim the device, publish findings when done.
  • Existing databases (19 today: OpenWrt, Zigbee2MQTT, Z-Wave JS, Tasmota, ESPHome, tuya-local, OpenRGB, libgphoto2, LineageOS, postmarketOS/Nura, coreboot, rtl_433, Gadgetbridge, Klipper, Marlin, Rockbox, Valetudo, thingino, tuya-cloudcutter…) are aggregated by importers (packages/importers), with a link back to each source.

If it is useful to you, a ⭐ helps people with the same devices find it.

Contributions don't have to be complete: a single verified fact about a protocol (a BLE characteristic, a checksum, UART pins) helps the next person or agent go faster. See Contribute.

See SPEC.md for the design and POLICY.md for what we accept.

npm install
npm run validate        # check every record against schema/device.schema.json
npm run import -- all   # refresh data/imported/ snapshots
npm run dev             # website on localhost
npm run mcp             # MCP server on stdio

Code: AGPL-3.0-or-later (see LICENSE). Data: CC BY-SA 4.0 (see LICENSE-DATA.md).

Frequently asked questions

What is OpenDeviceDB?

Check 21,000+ devices with open firmware or protocols before reverse engineering one.

How do I install OpenDeviceDB?

It runs on your machine. In Claude Code: claude mcp add opendevicedb -- npx -y @opendevicedb/mcp@0.3.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does OpenDeviceDB need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is OpenDeviceDB open source?

Yes. Its code is on GitHub under the AGPL-3.0 license.

Who maintains OpenDeviceDB?

It is published by opendevicedb. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.