Devotd Github
NewDeveloper tools

opendevicedb/opendevicedb mcp-v0.3.0 — Open Device Directory

opendevicedb/opendevicedb is a directory that provides information on devices with public protocols or firmware through a website, JSON API, and MCP server.

Repositoryopendevicedb/opendevicedb ↗

opendevicedb/opendevicedb is a directory that provides information on devices with public protocols or firmware through a website, JSON API, and MCP server.

GitHub description: Open directory of 29,000+ devices whose protocols or firmware are already open (OpenWrt, LineageOS, coreboot, QMK, Zigbee, printers, drones…), so nobody — human or AI agent — redoes the work. Website, JSON API, MCP server.

stars
★ 34
Forks
1
Language
TypeScript
License
AGPL-3.0
Latest release
mcp-v0.3.0
Read original source ↗View on GitHub ↗

The latest release of opendevicedb/opendevicedb is mcp-v0.3.0. According to the repository description, it indexes 29,000+ devices, including OpenWrt, LineageOS, coreboot, QMK and Zigbee-related devices, as well as printers and drones. The information can be checked on the website, the JSON API, and the MCP server. The provided FACTS do not list any specific changes in this release.

This directory aims to reduce repeated research by collecting protocol specifications or firmware information that is already public. Device pages show open firmware installation guides, difficulty, and risks. In the browser you can find connected or nearby devices by USB ID or Bluetooth name, and AI agents query the information through the MCP server. Materials from 19 existing databases are also gathered by an importer. It is written in TypeScript and uses the AGPL-3.0 license.

The nature of the material is closer to a list that merges several databases than to new measurement results. So it can serve as a starting point for finding device information and installation paths, but FACTS give no basis for interpreting the list itself as per-device verification results or performance comparisons. It is confirmed that there are 4 core test files, 20 importer test files, and 3 MCP test files, but that alone cannot be taken to mean that the information on all listed devices has been verified.