ESP32 Workbench plugin
ESP32 Workbench gives an agent 11 skills and 13 MCP tools for ESP32 firmware: pins, panics, build logs, partitions.
- 82 ★ on the repository
- Last commit
Extended access
Why this level
- The agent runs a local CLI and MCP server that read project code, logs and configuration.
- The Claude Code hook fires on every edit of `.c` and `.h` files.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/esp32-workbenchDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent runs a local CLI and MCP server that read project code, logs and configuration.
- The Claude Code hook fires on every edit of `.c` and `.h` files.
This is third-party code. Review the repository files before installing.
What it does
ESP32 Workbench is a plugin for ESP32 firmware development on ESP-IDF. Agents write plausible code that breaks on hardware: a flash pin used as chip select, an ADC2 read while Wi-Fi is on, a 2 KB stack for a TLS task. The plugin gives the agent verified data for nine chips (ESP32, S2, S3, C2, C3, C5, C6, H2, P4) with links to Espressif documents and deterministic tools, so it checks instead of guessing. It includes 11 skills from `esp32-repo-scout` to `esp32-pr-prepare`, the `esp32wb` CLI and the `esp32wb-mcp` MCP server with 13 tools: pin audit, Xtensa and RISC-V panic decoding, build log triage, partition table and `sdkconfig` checks. In Claude Code a hook pin-audits every edit of `.c` and `.h` files and sends errors back to the agent.
Who it is for. Embedded developers on ESP-IDF who hand firmware work to an agent and want to catch typical pin, stack and partition mistakes before flashing the board.
Good fit when
- A board crashes with Guru Meditation and the panic has to be decoded together with `addr2line`.
- An ESP-IDF project fails to build because of missing headers or IRAM overflow.
- Pins are chosen for I2C, SPI or ADC on a specific chip and conflicts are checked.
- Before a release, `sdkconfig`, the partition table, OTA slots and security settings are reviewed.
Not a fit when
- The firmware is not ESP-IDF and not for Espressif chips.
- Behavior has to be verified on real hardware: the tools analyze code, logs and configuration.
- Documentation search is needed without downloading references: the index is built from Espressif manuals.
Example request
Decode the panic from monitor.log with build/app.elf and say which stack or pointer is to blame.Limitations
The tools analyze code, logs and configuration and do not replace checks on hardware. Python 3.9 or newer is required, the core uses only the standard library, and the MCP server runs on plain `python3`. The Espressif documentation index is built with `esp32wb docs index`, which needs the `pypdf` package and downloads manuals for ESP32, S3, C3 and C6. The target chip is read from `CONFIG_IDF_TARGET` in `sdkconfig`. The pin guard hook works only in Claude Code. The last commit was made on 2 November 2026.
How to disable. Remove the plugin with `/plugin uninstall esp32-workbench@esp32-workbench` or delete the skills from `.claude/skills/` and `.agents/skills/` and the MCP entry from the agent configuration. Delete the project `missions/` folder manually.
FAQ
How do I install ESP32 Workbench in Claude Code?
With `/plugin marketplace add agodianel/esp32-claude-workbench` and `/plugin install esp32-workbench@esp32-workbench`. The plugin installs skills, the MCP server and the hook.
How do I set up a project in one command?
In the ESP-IDF project root run `uvx --from git+https://github.com/agodianel/esp32-claude-workbench esp32wb init . --agents all`. It creates `AGENTS.md` and `CLAUDE.md`, a `missions/` folder and wires skills and MCP for each agent.
Which chips are supported?
ESP32, S2, S3, C2, C3, C5, C6, H2 and P4. Pin facts come from Espressif documentation with a source link.
How do I decode a panic?
With `esp32wb crash monitor.log --elf build/app.elf` or the `crash_decode` MCP tool. It runs `addr2line` and names the cause, for example a NULL dereference or a stack overflow.
Does it work with Cursor and Codex?
Yes. Skills go to `.agents/skills/`, and the `--with-mcp` flag of `esp32wb install-skills` writes the MCP configuration for each agent.
Discussion
No questions or reviews yet.
Related
PluginsClaude Code skills and a Raspberry Pi testbench: the agent writes ESP32 firmware, flashes the board and tests it on hardware
24 skills for microcontroller firmware: build, flash, GDB debugging, UART, Modbus, CAN, logic analyzers and static analysis
A closed loop for STM32: the agent builds in Keil, flashes the board, reads serial output and finds the crashing line.
Espalier finds a codebase's unwritten conventions and records them as rules, reviewers and hooks for Claude Code, Codex, Copilot
A local codebase index with ten MCP tools: dependency graph, git history, code health and architectural decisions without re-grepping on every step
LabWired Core runs firmware on a virtual copy of a real chip and gives an agent UART and GPIO traces plus an exit code.
README in short
The README explains how the plugin helps an agent that needs verified chip data. Then come installation routes for each agent, the list of skills and tools, supported chips and a workflow from mission to PR.