esp32sim-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESP32SIM_PATH | No | Points at the esp32sim emulator binary elsewhere than the default location | |
| ESP32SIM_ROM_DIR | No | Points at another mask ROM directory. ROMs in an ESP-IDF install are found automatically. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sim_runB | Boots and simulates ESP32 firmware in a local emulator without hardware. Captures UART logs, FreeRTOS asserts, memory faults, and stop reason. |
| sim_scriptB | Simulates hardware interactions (button presses, GPIO levels, rotary encoder turns, touch, UART/console input) at specific emulated timestamps, capturing interactive firmware behavior. |
| sim_expectB | Runs firmware in simulation and asserts that specific text or regex patterns appear on UART. Ideal for automated unit & integration testing in a Red-Green-Refactor agent loop. |
| sim_screenshotC | Captures a snapshot image of the virtual LCD/TFT display buffer at a specified emulated time. |
| sim_list_boardsA | Returns the catalogue of all supported ESP32 chips, boards, displays, peripherals and capabilities. |
| sim_doctorA | Validates local environment: checks if esp32sim binary is installed, checks Rust/Cargo, and provides setup instructions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| esp32-tdd-loop | Interactive TDD prompt for developing ESP32 firmware in simulation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Supported ESP32 Boards and Chips | Full specifications of all hardware and peripherals modeled by esp32sim |
| Agent Guide for Simulated ESP32 Development | Step-by-step TDD workflow for writing and testing firmware without hardware |
TDQS
Scored across 6 tools
Most tools have distinct purposes: sim_run boots firmware, sim_script injects hardware interactions, sim_expect asserts UART output, and sim_screenshot captures the display. However, sim_run, sim_script, and sim_expect all execute simulation and their boundaries could occasionally blur, especially between generic running and scripted/asserted runs.
All tools use a consistent sim_ prefix and snake_case, making the set readable and predictable. The suffix conventions vary slightly (verbs like run/expect/list_boards vs nouns like screenshot/script/doctor), but this is a minor deviation rather than a real inconsistency.
Six tools is well-scoped for an ESP32 emulator MCP: run, script, expect, screenshot, environment check, and board catalogue. Each tool appears to earn its place without excessive surface area.
The surface covers core simulation workflows: booting firmware, injecting inputs, asserting UART output, capturing display state, and environment/board discovery. Minor gaps exist around explicit stop/reset or mid-run state inspection, but agents can likely work around these through the existing run/script/expect tools.