Opendevicedb
Open directory of 21,000+ devices whose protocols or firmware are already open (OpenWrt, LineageOS, coreboot, Zigbee, Z-Wave, appliances…), so nobody — human or AI agent — redoes the work. Website, JSON API, MCP server.
Install Opendevicedb
Pick your client, then add it in one click or paste the config.
No confirmed install command yet
We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for opendevicedb, and we’d rather show nothing than a guess you’d paste into your client.
Open setup steps on GitHubOverview
Security & health
What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.
Recent health check succeeded.
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
From the project README
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.
- Freedom: each project says what stays non-free (vendor blobs, modem, Wi-Fi…) and whether the vendor cloud is still needed; the directory filters devices that work with no cloud.
- Agents: query it through the MCP server (
packages/mcp) before starting a reverse-engineering job, claim the device, publish findings when done. - Existing databases (25 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, QMK, SANE,
OpenPrinting, libwacom, Betaflight, EdgeTX…) 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).
Reviews
No reviews yet — be the first to share how it worked for you.
Frequently Asked Questions about Opendevicedb
Related MCP servers
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/opendevicedb)<a href="https://allmcps.com/mcp/opendevicedb"><img src="https://allmcps.com/api/badge/opendevicedb?style=directory" alt="Opendevicedb on AllMCPs" /></a>