ToolBB-0049

DCP: Device Context Protocol for LLM agents on small microcontrollers

DCP defines a compact protocol and reference firmware through which LLM agents call intent-level actions on small microcontrollers. A host-side bridge exposes each intent as an MCP tool and checks capability tokens, units and ranges before anything reaches the board. The README lists 13 of 13 round-trip tests passing on an ESP32-WROOM-32 and an ESP32-S3.

Open original source github.com · Dongxu Yang

Claimed
Why this evidence label?

README reports UART round-trip tests passing on ESP32-WROOM-32 (CH340) and LILYGO T-Panel S3, plus measured footprint; numbers only, no captures or photos.

How we check entries
Preview image for DCP: Device Context Protocol for LLM agents on small microcontrollers
The source's own preview image, from github.com.

Briefing

A DCP frame is a 6-byte header plus a CBOR payload. A typical set_brightness(50) call is 19 bytes, against about 180 for the MCP JSON-RPC equivalent. The README reports the DCP layer at 27.6 KB of flash and 0.6 KB of RAM on an ESP32-WROOM-32, above the original 16 KB flash target. The bridge signs and verifies HMAC-SHA256 tokens and talks to devices over UART, MQTT or BLE.

The firmware also builds for the ESP32-C3, C6, H2, P4 and ESP8266, but only the ESP32 and ESP32-S3 are marked as run on hardware. A companion arXiv paper (2605.26159) compares DCP with IoT-MCP. The README gives test counts and charts, not captures or photos of the board runs.

From the GitHub API

Repository facts

Repository facts for device-context-protocol/dcp, from the GitHub API
Repositorydevice-context-protocol/dcp
Stars62
LicenseMIT Permissive
LanguagePython
Last push27 May 2026 5 mo ago

Tags

Board

Report a problem with this entry