Zigbee2mqtt-mcp Server

Zigbee2mqtt-mcp is an MCP integration. Administer a Zigbee2MQTT estate: health, mesh diagnostics, OTA, pairing, device management.

Packages and local setup

The published npm package is zigbee2mqtt-mcp, version 0.7.0. Its declared MCP transport is stdio.

The package declares Z2M_MQTT_URL (required): MQTT broker URL used by Zigbee2MQTT, e.g. mqtt://192.168.1.10:1883. Supports mqtt://, mqtts://, ws:// and wss://. This is the broker, not the Zigbee2MQTT frontend port.; Z2M_MQTT_USERNAME: MQTT broker username, if the broker requires authentication.; Z2M_MQTT_PASSWORD: MQTT broker password, if the broker requires authentication.; Z2M_BASE_TOPIC: Zigbee2MQTT base topic. Must match mqtt.base_topic in configuration.yaml. Defaults to zigbee2mqtt.; Z2M_WRITE_MODE: Tool exposure tier: off (read-only), safe (default; adds non-destructive writes such as pairing, options, rename and binding) or full (adds device removal, OTA flashing, Touchlink and bridge restart)..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.7.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.