{"repo":"device-context-protocol/dcp","free":true,"listed":false,"github":"https://github.com/device-context-protocol/dcp","clone":"git clone https://github.com/device-context-protocol/dcp.git","description":"Device Context Protocol — bridge LLM agents to physical devices. Sub-50-byte frames, 27.6KB flash / 0.6KB RAM measured on ESP32, capability-scoped and safe by design. Complementary to MCP. Paper: arXiv:2605.26159","language":"Python","stars":56,"topics":["agent","arduino","bridge","cbor","device-control","embedded","esp32","hardware","iot","llm"],"license":"MIT","category":"ai-agents","readme_excerpt":"DCP — Device Context Protocol Status: Draft v0.3 — May 2026 · Hardware-validated on ESP32-WROOM-32 A protocol that lets LLM agents safely control physical devices, down to dollar-class microcontrollers. Intent-level, transport-agnostic, capability-scoped. Compact wire format (sub-50-byte frames). Self-contained firmware: under 1 KB of RAM, 28 KB of flash. Complementary to MCP — a reference Bridge translates DCP ↔ MCP so any MCP host (Claude Desktop, Claude Code, IDE assistants) works zero-config. Contents - Why DCP? - Design principles - Architecture - Quickstart - Add a feature in 5 steps - Recipes — five ready-to-flash device skeletons - Wire format · full SPEC.md - Manifest - Roadmap - Design rationale: docs/RATIONALE.md — why not MCP-on-MCU, why not WoT, why not Matter. Why DCP? MCP is excellent for SaaS tools, but assumes JSON-RPC over WebSocket and runtime tool discovery. On an MCU with 32 KB of RAM, that's a non-starter. DCP keeps MCP's mental model (manifest + tool calls) but: - compiles to a compact CBOR wire format - uses a static intent table (no runtime negotiation) - moves safety enforcement to a Bridge process A reference Bridge translates DCP ↔ MCP , so any MCP-compatible LLM works out of the box. DCP is the last mile to physical hardware. Why this matters in one chart: the protocol's schema decides how many hallucinated or adversarial calls are stopped before any byte reaches a device. DCP catches all six categories at the wire layer; the others catch what the","default_branch":null,"files":null,"tree":[],"storefront":"/r/device-context-protocol","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/device-context-protocol/dcp/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}