mcp-server-zwave-js-ui
This server provides read-only introspection of a Z-Wave network through Z-Wave JS UI, allowing you to monitor and inspect your Z-Wave mesh, controller, and connected devices.
Get controller/network summary (
zwave_controller_info): Retrieve the controller's home ID, type, SDK/API/firmware versions, RF region, primary/inclusion state, and node counts — useful for a quick health snapshot of the mesh.List all Z-Wave nodes (
zwave_list_nodes): Get a one-line summary of every node on the network, including node ID, name, location, status (alive/asleep/dead), readiness, security class, manufacturer, device label, firmware version, and interview stage.Get full node details (
zwave_node_info): Retrieve comprehensive information about a specific node, including device class, supported command classes, endpoint count, security class, protocol version, last-seen time, and signal statistics.List node values (
zwave_node_values): View a specific node's current sensor/actuator readings and state values (excluding configuration parameters), along with metadata such as labels, units, types, ranges, and writeability.List node configuration parameters (
zwave_node_config): View a specific node's manufacturer-defined configuration parameters (e.g., LED behavior, report intervals, motion sensitivity) with current values, defaults, allowed ranges/states, units, and sizes. Note: setting parameters is a planned future feature.
Integrates with Z-Wave JS UI to manage a Z-Wave network, providing tools for controller info, node listing, node details, values, and configuration parameters.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-zwave-js-uilist all Z-Wave nodes"
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.
mcp-server-zwave-js-ui
An MCP server for managing a Z-Wave network
through Z-Wave JS UI. It connects to
the zwave-js-server WebSocket that Z-Wave JS UI exposes and surfaces the mesh
— controller, nodes, values, and configuration parameters — as tools an MCP
client (e.g. Claude) can call.
Status: early / read-only. This first release covers read-only introspection. Write control and administrative operations are on the roadmap — see Roadmap.
Quickstart
In Z-Wave JS UI, make sure the Z-Wave JS Server WebSocket is enabled (Settings → Home Assistant → WS Server; default port
3000). See What it connects to.Add the server to Claude Code, pointing
ZWAVE_JS_URLat that WebSocket. No manual install needed —uvxfetches and runs the published package:claude mcp add zwave-js-ui \ --env ZWAVE_JS_URL=ws://<host>:3000 \ -- uvx mcp-server-zwave-js-uiAsk Claude about your mesh — it calls the read-only tools to answer:
"Which Z-Wave controller am I running, and how many nodes are on the network?"
"List my Z-Wave nodes and flag any that are dead or asleep."
For other MCP clients, isolated installs, and configuration details, see the sections below.
Related MCP server: openhab
What it connects to
Z-Wave JS UI runs two servers: the web UI (default port 8091) and the
Z-Wave JS Server WebSocket (default port 3000) that Home Assistant and
this MCP server talk to. Point ZWAVE_JS_URL at the WebSocket, not the UI.
Install
Requires Python 3.12+.
pip install mcp-server-zwave-js-ui
# or, isolated:
pipx install mcp-server-zwave-js-ui
# or, no install:
uvx mcp-server-zwave-js-uiConfigure
Variable | Default | Description |
|
| WebSocket URL of the Z-Wave JS Server. |
Use with Claude Code
claude mcp add zwave-js-ui \
--env ZWAVE_JS_URL=ws://borg:3002 \
-- uvx mcp-server-zwave-js-uiOr add it to an MCP client config directly:
{
"mcpServers": {
"zwave-js-ui": {
"command": "uvx",
"args": ["mcp-server-zwave-js-ui"],
"env": { "ZWAVE_JS_URL": "ws://borg:3002" }
}
}
}Tools
Tool | Description |
| Controller and network summary (home id, versions, RF region, node counts). |
| One-line summary of every node (status, readiness, security, device). |
| Full detail for a node (device class, command classes, endpoints, signal). |
| A node's current values, excluding configuration parameters. |
| A node's configuration parameters with current values and metadata. |
Roadmap
Level 2 — read/write: set values (on/off/dim), set configuration parameters, manage association groups. Mutating tools will be gated behind a
ZWAVE_JS_READ_ONLYflag.Level 3 — admin/lifecycle: inclusion/exclusion, re-interview, network heal / rebuild routes, OTA firmware update.
Development
git clone https://github.com/cacack/mcp-server-zwave-js-ui
cd mcp-server-zwave-js-ui
uv venv --python 3.13 && source .venv/bin/activate
uv pip install -e ".[dev]"
pytest
ruff check . && ruff format --check .See CLAUDE.md for architecture and design notes.
License
Maintenance
Resources
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 InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/cacack/mcp-server-zwave-js-ui'
If you have feedback or need assistance with the MCP directory API, please join our Discord server