Briefing
The firmware builds in PlatformIO with two board profiles, an ESP32-C3 DevKitM-1 and a conservative ESP32-S3, each with a fixed list of allowed GPIOs. On the S3, the boot straps, USB pins, UART bridge pins and flash and PSRAM pins are blocked. The host reads that policy from the board and checks named endpoints against it before changing a mode or writing a pin. A host-side daemon can expose the bridged UART as a local PTY.
The MCP server can offer the raw GPIO tools, only the named endpoint tools, or both, and an endpoint file can define its own tool names such as reset_pulse. The README leaves power sequencing to external bench equipment and warns against mapping power to a GPIO unless that is intended.
Written by the Boards & Bots curator
From the GitHub API
Repository facts
| Repository | jbp-sy/ |
|---|---|
| Stars | 1 |
| Language | Python |
| Last push | 5 May 2026 5 mo ago |