ESP32 Control MCP server

ESP32 MCP Server

Control and read ESP32 IoT devices directly from AI agents (Claude, Cursor, any MCP client).

• esp32.status — online / chip / free heap / uptime
• esp32.gpio_set — set a GPIO high/low
• esp32.gpio_read — read a digital pin
• esp32.adc_read — read analog voltage (mV)
• esp32.send_command — raw AT/application command
• esp32.reboot — reboot the device

Architecture

AI agent (Claude/Cursor)  →  this MCP server (Python)  →  ESP32 REST API  →  device

The ESP32 runs a tiny MicroPython firmware (esp32_firmware/main.py) exposing a lightweight REST API on port 80. The MCP server talks to it over HTTP — works locally and remotely.

Quick start

1. Flash the ESP32 firmware

or you can set STA mode inside the firmware to join your network.

1. Install MicroPython on your ESP32.
2. Upload esp32_firmware/main.py as main.py (Thonny or mpremote).
3. Power on — the device opens a WiFi AP named ESP32-MCP (password 12345678)

2. Run the MCP server

pip install esp32-mcp
export ESP32_HOST=http://192.168.4.1     # device address (AP default)
esp32-mcp                                  # stdio transport (local MCP client)

For remote agents, run with HTTP transport:

uv run esp32-mcp --transport http --port 8000

3. Add to your AI client

Claude Desktop (claudedesktopconfig.json):

{
  "mcpServers": {
    "esp32": {
      "command": "esp32-mcp",
      "env": { "ESP32_HOST": "http://192.168.4.1" }
    }
  }
}

Cursor: Settings → MCP → Add server → esp32-mcp with env ESP32_HOST.

Then just ask: "turn GPIO 2 on", "what's the ADC reading on pin 34?", "reboot the device".

Configuration

Safety

in the firmware to change).

• GPIO outputs are limited to pins 2, 4, 5, 18, 19 by default (edit GPIO_OUT

exposing to the internet.

• The firmware only listens on its own network; change the AP password before

Pricing

Free is not a trial — core tools work forever. Upgrade when you need scale.

License

MIT