I have a few gadgets that only ship a Windows app (an AIO cooler LCD, an RGB controller, a mouse), so I built usb-rea to do the boring part of reverse engineering them.
You capture USB traffic while clicking settings in the vendor app (usbmon on Linux, USBPcap on Windows), label what you clicked, and usb-rea infers the command structure: constant bytes, counters, linear values, lookup tables, checksums like CRC16. It writes a Markdown report where every claim links to Wireshark frame numbers, plus a standalone pyusb driver.
It runs as an MCP server, so in Cursor the agent can drive the whole loop (start capture, mark actions, diff, report, scaffold the driver). replay_packet refuses to send anything to a device unless you confirm it.
Setup in Cursor (~/.cursor/mcp.json), no install needed with uv:
{"mcpServers": {"usb-rea": {"command": "uvx", "args": ["--from", "usb-rea", "usb-rea", "mcp"]}}}
You can try it without hardware: pip install usb-rea then usb-rea demo --device fan builds a synthetic capture and recovers the protocol. On real protocols it reproduces the NZXT Kraken X fan command and SteelSeries Rival 100 tables byte for byte, matching liquidctl and rivalcfg (checked in CI).
It is alpha and MIT licensed: GitHub - emirmrkaljevic/usb-rea: Reverse Engineer any USB gadget: capture vendor-app traffic, infer the protocol with evidence, generate an open Python/libusb driver. CLI + MCP server. · GitHub
If you have a Windows-only USB device, I’m happy to run a capture through it.