esp32-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESP32_MCP_URL | No | Base URL of the board | http://esp32-mcp.local |
| ESP32_MCP_TOKEN | No | Sent as X-Api-Token when set | |
| ESP32_MCP_TIMEOUT | No | HTTP timeout in seconds | 5.0 |
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| esp32_healthA | Read board health: firmware version, IP address, hostname, uptime, free heap and the relay table (index, name, pin, state). Call this first to learn what the board exposes. |
| esp32_read_sensorsA | Read every sensor configured in the firmware: the internal chip temperature and each analog channel, with raw ADC counts, millivolts and a scaled value. |
| esp32_set_relayA | Switch one relay on or off. Relay indexes are 1 based and are listed by esp32_health. The call is idempotent. |
| esp32_gpio_readA | Read the mode and digital level of one GPIO pin. Only pins in the firmware allow list can be read. |
| esp32_gpio_writeA | Set a GPIO pin mode (output, input, input_pullup) and optionally drive it high or low. Pass value only, mode only, or both. Only pins in the firmware allow list can be changed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct action: health (board identity/diagnostics), read_sensors (sensor values), set_relay (relay control), gpio_read, gpio_write. The only mild overlap is that esp32_health also reports the relay table and health metrics while esp32_read_sensors reports chip temperature, but the descriptions make the boundary clear enough.
All tools share the esp32_ prefix and a consistent snake_case form. Minor deviation: read_sensors/set_relay use verb_noun ordering while gpio_read/gpio_write use noun_verb, though the gpio pair is internally consistent and readable.
Five tools is a tight, well-scoped surface for a microcontroller: one discovery, one sensor read, one relay control, and a GPIO read/write pair. Nothing feels redundant or padded.
Core lifecycle is covered: discovery, sensor reading, relay actuation, and GPIO read/write. Gaps exist for reset/reboot, OTA/firmware update, and analog/PWM output, but these are minor and can be worked around for typical use.