zigbee2mqtt-mcp
Administers a Zigbee2MQTT mesh: health, link quality, OTA updates, pairing, binding and device options.
Add it to your client
Communitynpx -y zigbee2mqtt-mcp
{
"mcpServers": {
"zigbee2mqtt-mcp": {
"command": "npx",
"args": [
"-y",
"zigbee2mqtt-mcp"
]
}
}
}- Transport
- stdio
- Runtime
- Node
- License
- MIT
- Stars
- 29
Turning a light on is already solved; the gap this fills is the bridge layer that Home Assistant does not expose — mesh topology, weak links, devices stuck rejoining, stale batteries, firmware availability, permit_join, reporting intervals and bindings. It speaks the Zigbee2MQTT bridge API over MQTT directly, so it works whether the front end is Home Assistant, Node-RED, openHAB or nothing at all. Two design notes carry the implementation: there is no database, because Zigbee2MQTT publishes bridge topics as retained messages and a fresh subscription rebuilds the whole picture in a few hundred milliseconds, and every bridge request carries a transaction id matched to its response so concurrent calls cannot cross wires. Destructive operations sit behind a write mode plus an explicit confirm argument. Tested against Zigbee2MQTT 2.x.
Similar MCP servers
Hass-MCP
MCP serverCommunity Home Assistant server that also edits dashboards.
Home Assistant MCP Server
MCP serverHome Assistant's built-in server for exposing the house to an LLM.
Bluesky MCP Server
MCP serverTurns a chat client into a Bluesky reader and poster over the AT Protocol, with eighteen tools.

Comments(0)
Sign in to comment