**administering ** Zigbee2MQTT 부동산에 대한 모델 콘텍스트 프로토콜 서버.

대부분의 Zigbee 통합은 이미 조수가 켜집니다. 이것은 층 underneath에 대한 것입니다 : 메쉬 건강, 약한 링크, rejoining, stale 배터리, 펌웨어 업데이트, 페어링, 바인딩,보고 간격 및 장치 옵션 - 일반적으로 Zigbee2MQTT 프론트 엔드를 엽니 다.

Zigbee2MQTT MQTT 브리지 API에 직접 이야기하므로 홈 보조, Node-RED, openHAB 또는 전혀 사용할 수 없습니다. Zigbee2MQTT 2.x에 대해 테스트했습니다. 몇몇 도구는 bridge/health], device/binds/clear 및 OTA 스케줄링 주제를 포함한 브리지 엔드 포인트에 의존합니다.

왜 이 존재

이미 홈 어시스턴트를 실행하면 Zigbee 장치가 노출되어 조수가 제어 할 수 있습니다. 어떤 홈 조수는 *not * 노출 다리 자체입니다: 링크 품질, 메쉬 토폴로지, 인터뷰 국가, OTA 가용성, permit_join, 장치 옵션, 바인딩 및보고 구성. 이 서버는 정확히 그 간격을 채웁니다.

디자인

• **No 데이터베이스.

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 cannot cross wires.
• Tiered writes. Destructive operations are gated behind a write mode and an explicit confirm argument.

Install

Requires Node.js 22 or newer and network access to the MQTT broker that Zigbee2MQTT uses.

npx zigbee2mqtt-mcp

VS Code / GitHub Copilot

Add to your MCP configuration:

{
  "servers": {
    "zigbee2mqtt": {
      "command": "npx",
      "args": ["-y", "zigbee2mqtt-mcp"],
      "env": {
        "Z2M_MQTT_URL": "mqtt://192.168.1.10:1883",
        "Z2M_MQTT_USERNAME": "mqtt",
        "Z2M_MQTT_PASSWORD": "${input:z2mPassword}"
      }
    }
  }
}

Claude Desktop

{
  "mcpServers": {
    "zigbee2mqtt": {