Which integrations are available for this server?

Provides tools for listing and inspecting Zigbee devices, reading and changing their state, and managing the Zigbee2MQTT bridge through its frontend websocket API.

How do I use Zigbee2MQTT-MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Zigbee2MQTT-MCP turn off the bedroom lamp" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Zigbee2MQTT-MCP

by loryanstrant

Overview Schema Related Servers Score Discussions

Python

Hybrid

Zigbee2MQTT-MCP

An MCP server for Zigbee2MQTT. It lets an LLM (or any MCP client) list and inspect your Zigbee devices, read and change their state, and manage the bridge — all through the Zigbee2MQTT frontend websocket API, so it needs no direct access to your MQTT broker.

Why the frontend API?

Zigbee2MQTT's frontend exposes a websocket at /api that proxies MQTT traffic as JSON {"topic": ..., "payload": ...} messages (base topic already stripped). Talking to it instead of the MQTT broker means:

No broker dependency — works even if you don't expose MQTT on the network.
One HTTPS endpoint — reuses your existing reverse proxy / TLS.
Auth-ready — supports the frontend auth_token when you enable it.

Requests that change the bridge (bridge/request/*) are correlated to their bridge/response/* reply via a transaction id, with per-call timeouts. The retained device snapshot is cached on connect, so reads are instant and the connection auto-reconnects (re-priming the cache) if it drops.

Related MCP server: mcp2mqtt

Tools

Read

Tool	Description
`connection_status`	Websocket health + cache readiness
`list_devices`	All devices (compact summary or `detailed=true`)
`find_devices`	Search by name / model / vendor / address
`get_device`	Full definition/metadata for one device
`get_device_state`	Current cached state (+ optional `refresh`)
`list_groups`	All groups and their members
`get_bridge_info`	Version, coordinator, config, permit-join state
`get_bridge_state` / `get_bridge_health`	Bridge online state / health metrics
`get_network_map`	Scan and return the Zigbee mesh map

Control

Tool	Description
`set_device_state`	Set state — `{"state":"ON"}`, brightness, colour, cover position, …
`ota_check`	Check for a firmware update
`permit_join`*	Allow/deny new devices joining
`rename_device`*	Rename a device
`remove_device`*	Unpair a device
`set_device_options`* / `configure_device`*	Per-device options / re-configure
`ota_update`*	Perform a firmware update
`create_group`* / `remove_group`* / `group_add_member`* / `group_remove_member`*	Group management

* Protected: disabled unless Z2M_ALLOW_DESTRUCTIVE=true. Reads and set_device_state are always available.

Configuration

All configuration is via environment variables (see .env.example):

Variable	Default	Description
`Z2M_FRONTEND_URL`	`http://localhost:8080`	Base URL of the Zigbee2MQTT frontend. `ws(s)://…/api` is derived from it
`Z2M_AUTH_TOKEN`	(empty)	Frontend `auth_token`, appended as `?token=…`
`Z2M_TLS_INSECURE`	`false`	Skip TLS verification for `wss://` (self-signed)
`Z2M_REQUEST_TIMEOUT`	`15`	Seconds to wait for a `bridge/response`
`Z2M_CONNECT_TIMEOUT`	`20`	Seconds to wait for the initial snapshot at startup
`Z2M_ALLOW_DESTRUCTIVE`	`false`	Enable the protected management tools
`MCP_TRANSPORT`	`http`	`http` (streamable HTTP) or `stdio`
`MCP_HOST` / `MCP_PORT` / `MCP_PATH`	`0.0.0.0` / `8080` / `/mcp`	HTTP bind + path
`MCP_HOST_PROTECTION`	`false`	DNS-rebind Host/Origin protection: `false`, `true`, or `auto`
`MCP_ALLOWED_HOSTS`	`*.strant.casa,localhost,127.0.0.1`	Host allowlist (used when protection is on)
`MCP_LOG_LEVEL`	`INFO`	Log level

Running

Docker (recommended)

docker run -d --name zigbee2mqtt-mcp -p 8080:8080 \
  -e Z2M_FRONTEND_URL=https://zigbee2mqtt.example.com \
  ghcr.io/loryanstrant/zigbee2mqtt-mcp:latest

The MCP endpoint is then at http://<host>:8080/mcp.

Or with Compose — copy .env.example to .env, edit it, and:

docker compose up -d

Local (Python 3.11+)

pip install .
Z2M_FRONTEND_URL=https://zigbee2mqtt.example.com python -m zigbee2mqtt_mcp

stdio (local MCP client, e.g. Claude Desktop)

{
  "mcpServers": {
    "zigbee2mqtt": {
      "command": "python",
      "args": ["-m", "zigbee2mqtt_mcp"],
      "env": {
        "MCP_TRANSPORT": "stdio",
        "Z2M_FRONTEND_URL": "https://zigbee2mqtt.example.com"
      }
    }
  }
}

Development

python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]"
pytest

Security

This server exposes control of your Zigbee network. Bind it to a trusted network (LAN/VPN) or an authenticating proxy, keep Z2M_ALLOW_DESTRUCTIVE=false unless you need management tools, and never commit a populated .env. See SECURITY.md.

License

MIT — see LICENSE.

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/loryanstrant/Zigbee2MQTT-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server