{"repo":"alexpfau/zigbee2mqtt-mcp","free":true,"listed":false,"github":"https://github.com/alexpfau/zigbee2mqtt-mcp","clone":"git clone https://github.com/alexpfau/zigbee2mqtt-mcp.git","description":"MCP server for administering a Zigbee2MQTT estate: health reporting, mesh diagnostics, OTA updates, pairing, binding and device options over the MQTT bridge API.","language":"TypeScript","stars":29,"topics":["claude","copilot","home-automation","iot","mcp","model-context-protocol","mqtt","smart-home","typescript","zigbee"],"license":"MIT","category":"mcp-servers","readme_excerpt":"zigbee2mqtt-mcp A Model Context Protocol server for administering a Zigbee2MQTT estate. Most Zigbee integrations already let an assistant turn a light on. This one is for the layer underneath: mesh health, weak links, devices that keep rejoining, stale batteries, firmware updates, pairing, binding, reporting intervals and device options — the things you normally open the Zigbee2MQTT frontend for. It talks directly to the Zigbee2MQTT MQTT bridge API, so it works regardless of whether you use Home Assistant, Node-RED, openHAB or nothing at all. Tested against Zigbee2MQTT 2.x; several tools depend on bridge endpoints that only exist there, including bridge/health , device/binds/clear and the OTA scheduling topics. Why this exists If you already run Home Assistant, your Zigbee devices are exposed there and an assistant can control them. What Home Assistant does not expose is the bridge itself: link quality, mesh topology, interview state, OTA availability, permit join , device options, bindings and reporting configuration. This server fills exactly that gap. Design - No database. Zigbee2MQTT publishes its bridge topics as retained messages, so a fresh subscription yields a complete picture in a few hundred milliseconds. The server keeps only the latest payload per topic in memory. - No daemon. Pure stdio. It starts and dies with the MCP session. - Correlated requests. Every bridge/request/ carries a transaction id and is matched to its bridge/response/ , so concurrent calls canno","default_branch":null,"files":null,"tree":[],"storefront":"/r/alexpfau","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/alexpfau/zigbee2mqtt-mcp/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}