Skip to content
↑↓navigate↵openescclose
Claude+372Whisper+228LangChain+168Codex+223NotebookLM+276DALL-E 3+192DeepL+249n8n+208Topaz Video AI+153LlamaIndex+161
zigbee2mqtt-mcp logo
#197 · of 445 · by weekly downloadsMCP server

zigbee2mqtt-mcp

Administers a Zigbee2MQTT mesh: health, link quality, OTA updates, pairing, binding and device options.

0
SaveVisit website ↗
Rank
#197
of 445 · by weekly downloads
Weekly downloads
97
npm + PyPI, last 7 days
GitHub stars
29
Repository on GitHub

Add it to your client

Community
Install
npx -y zigbee2mqtt-mcp
mcpServers
{
  "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.

Comments(0)

Sign in to comment

No comments yet — be the first.

Similar MCP servers

Report this comment

Why are you reporting this?