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_expectA | 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
Each tool targets a distinct action (run, script inputs, assert, list boards, screenshot, validate env), and descriptions clarify boundaries. Minor overlap exists between sim_run and sim_expect, since both boot firmware, but the assertion-focused purpose of sim_expect distinguishes it well enough.
All tools use a consistent sim_ prefix with snake_case naming (sim_run, sim_script, sim_expect, sim_list_boards, sim_screenshot, sim_doctor). The verb/noun pattern is predictable and readable throughout.
Six tools is well-scoped for an ESP32 simulation server, covering execution, input scripting, assertions, board discovery, display capture, and environment validation. Each tool clearly earns its place with no redundancy.
The surface covers the core firmware-simulation lifecycle: boot/run, drive inputs, assert UART output, enumerate boards, capture display, and validate environment. Minor gaps like reading GPIO output state or finer run-control (pause/step) are worth noting but workable.