Zigbee2mqtt MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 138 installs a week from npm. Last commit 23 Oct 2026.
Administer a Zigbee2MQTT estate: health, mesh diagnostics, OTA, pairing, device management.
Today is the operative word: we check Zigbee2mqtt MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add zigbee2mqtt-mcp -e 'Z2M_MQTT_URL=<Z2M_MQTT_URL>' -- npx -y zigbee2mqtt-mcp
{
"mcpServers": {
"zigbee2mqtt-mcp": {
"command": "npx",
"args": [
"-y",
"zigbee2mqtt-mcp"
],
"env": {
"Z2M_MQTT_URL": "<Z2M_MQTT_URL>"
}
}
}
}
[mcp_servers.zigbee2mqtt-mcp]
command = "npx"
args = ["-y", "zigbee2mqtt-mcp"]
env = { Z2M_MQTT_URL = "<Z2M_MQTT_URL>" }
{
"mcpServers": {
"zigbee2mqtt-mcp": {
"command": "npx",
"args": [
"-y",
"zigbee2mqtt-mcp"
],
"env": {
"Z2M_MQTT_URL": "<Z2M_MQTT_URL>"
}
}
}
}
{
"servers": {
"zigbee2mqtt-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"zigbee2mqtt-mcp"
],
"env": {
"Z2M_MQTT_URL": "<Z2M_MQTT_URL>"
}
}
}
}
Put your own value in place of
<Z2M_MQTT_URL> (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).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
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)).
Development tooling MCP server with process management, proxy, and frontend diagnostics
Read-only Spring Boot runtime evidence for agents: beans, routes, health, startup.
Local MCP server for AI-assisted Apache Tomcat management and diagnostics
DMARC monitoring, SPF/DKIM diagnostics, reports, domains and MSP client management with Suped.
Redis health, BullMQ queue monitoring, memory analysis, and slow query diagnostics
MCP server for Homey Pro: 60 tools for devices, flows, energy, and Z-Wave/Zigbee diagnostics.
MCP server for read-only Linux system administration, diagnostics, and troubleshooting
Remote enterprise management of Android devices and apps
Answers built from our own checks of this server.