ToolBB-0067

smarthome-builder-mcp: an MCP server for Home Assistant, Node-RED and ESPHome

smarthome-builder-mcp exposes a Home Assistant installation, including its Node-RED flows and ESPHome devices, to an AI assistant as 51 MCP tools. For ESPHome devices it edits and validates YAML, compiles, flashes over the air and reads logs. It backs up every change first, previews writes as a diff and always asks before flashing. The README calls it alpha.

Open original source github.com · xMase

Claimed
Why this evidence label?

README describes the tools and safety gates with example requests; no logs or photos of a device being flashed.

How we check entries
Preview image for smarthome-builder-mcp: an MCP server for Home Assistant, Node-RED and ESPHome
The source's own preview image, from github.com.

Briefing

Of the 51 tools, 30 cover Node-RED, 10 Home Assistant and 11 ESPHome. In the default propose mode, a Node-RED change returns a diff and writes nothing until it is called again with confirm=true; auto mode skips that step, except for ESPHome flashing. A sha256 check blocks an ESPHome write if the file changed since the preview. The server always refuses Home Assistant restarts, host reboots and recorder purges, and previews sensitive calls such as unlocking a lock.

The README says scripts and automations can still reach the gated services indirectly, and Home Assistant service calls have no backup. It runs on one installation, the author's. It is based on nr-mcp from NXTAssist.ai and is MIT-licensed.

From the GitHub API

Repository facts

Repository facts for xmase/smarthome-builder-mcp, from the GitHub API
Repositoryxmase/smarthome-builder-mcp
Stars0
LicenseMIT Permissive
LanguagePython
Last push15 Oct 2026 15 d ago

Tags

Board
Agent

Report a problem with this entry