ToolBB-0095

ESPHome-MCP: drive the ESPHome 2026.6 Device Builder from an agent

ESPHome-MCP connects an agent to the ESPHome Device Builder through the WebSocket protocol it adopted in 2026.6. Its 16 tools edit and validate YAML, stream logs, decode crash backtraces and compile and OTA-flash firmware. Flash tools are marked destructive, and an offline device reports a deferred flash. The author expects to archive it once ESPHome ships its own MCP server.

Open original source github.com · Loryan Strant

Claimed
Why this evidence label?

The author describes it but shows no evidence we could check yet.

How we check entries
Preview image for ESPHome-MCP: drive the ESPHome 2026.6 Device Builder from an agent
The source's own preview image, from github.com.

Briefing

ESPHome 2026.6 replaced the dashboard's HTTP API with a WebSocket command protocol, and the README says the older MCP servers' config tools return garbage against it. This fork keeps the FastMCP tool layer of kdkavanagh/esphome-mcp and rewrites the transport for Device Builder 1.14.x. It runs in Docker on port 8080 over Streamable HTTP, or over stdio, and the container's health check completes a full MCP handshake.

The README says version 2026.06.0 reported every device as unknown on ESPHome 2026.7 and later, and could report a successful install for firmware it never flashed; 2026.08.0 fixed both. Device Builder 1.15 and later ships its own MCP server with about 22 tools. Five tools here, including log streaming and backtrace decoding, have no upstream equivalent, and the author intends to offer them upstream.

From the GitHub API

Repository facts

Repository facts for loryanstrant/esphome-mcp, from the GitHub API
Repositoryloryanstrant/esphome-mcp
Stars31
LicenseMIT Permissive
LanguagePython
Last push28 Sep 2026 32 d ago

Tags

Board
Agent

Report a problem with this entry