wiz-light-mcp
Click on "Deploy 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., "@wiz-light-mcp set living room to sunset mode"
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.
wiz-light-mcp
MCP server for controlling WiZ smart lights from Claude Code and other MCP clients.
"Turn my light blue" / "Set focus mode" / "Discover all my lights" — right from a Claude conversation.
Features
Discover WiZ bulbs on your local network automatically
Power control — on, off, toggle
Color — set any RGB color
Temperature — warm white (2200K) to cool daylight (6500K)
Scenes — 32 built-in scenes (Ocean, Focus, Party, Sunset, and more)
Multi-bulb — control individual bulbs by name or all at once
Zero config — auto-discovers bulbs, no IP addresses to configure
Zero dependencies — just the MCP SDK and Node.js built-in UDP
Related MCP server: elgato-keylight
Quick Start
Claude Code
claude mcp add wiz-light -- npx -y wiz-light-mcpOr add manually to ~/.claude.json:
{
"mcpServers": {
"wiz-light": {
"command": "npx",
"args": ["-y", "wiz-light-mcp"]
}
}
}Then in any Claude Code conversation:
You: discover my lights
You: turn the bedroom light to sunset mode
You: set all lights to 50% brightness
You: what color is the office light?Other MCP Clients
Any MCP-compatible client can use this server. Run with stdio transport:
npx wiz-light-mcpTools
Tool | Description |
| Scan the network for WiZ bulbs |
| List previously discovered bulbs |
| Turn on a light (optional brightness) |
| Turn off a light |
| Toggle a light's power state |
| Set RGB color |
| Set white color temperature (2200-6500K) |
| Activate a built-in scene by name or ID |
| Get current state of a light |
| List all 32 available scenes |
Scenes
Ocean, Romance, Sunset, Party, Fireplace, Cozy, Forest, Pastel Colors, Wake Up, Bedtime, Warm White, Daylight, Cool White, Night Light, Focus, Relax, True Colors, TV Time, Plant Growth, Spring, Summer, Fall, Deep Dive, Jungle, Mojito, Club, Christmas, Halloween, Candlelight, Golden White, Pulse, Steampunk
Requirements
A WiZ smart bulb on the same WiFi network
Node.js 18+
"Allow Local Communication" enabled in the WiZ app
How It Works
WiZ bulbs run a local UDP server on port 38899 that accepts JSON commands — no cloud, no API keys, no authentication. This MCP server sends UDP packets directly to your bulbs on the local network.
Troubleshooting
No bulbs found: Make sure bulbs are powered on, on the same WiFi, and "Allow Local Communication" is enabled in the WiZ app.
Bulb IP changed: Run discover_lights again. Consider setting a static IP in your router's DHCP settings.
Timeout errors: The bulb may be unresponsive. Try power-cycling it.
License
MIT
Available Tools
10 toolsdiscover_lightsARead-only
Scan the local network for WiZ smart bulbs via UDP broadcast
Inputs: no named parameters.
get_statusARead-only
Get the current state of a WiZ bulb (power, brightness, color, scene, etc.)
Inputs: target (required).
list_lightsARead-only
List all previously discovered WiZ bulbs (from the in-memory registry)
Inputs: no named parameters.
list_scenesARead-only
List all 32 available WiZ light scenes with their IDs
Inputs: no named parameters.
set_colorB
Set the RGB color of one or more WiZ bulbs
Inputs: b (required), g (required), r (required), target (required), +1 more.
set_sceneB
Activate a WiZ scene by name or ID on one or more bulbs
Inputs: scene (required), target (required), speed.
set_temperatureA
Set the color temperature of one or more WiZ bulbs (warm to cool white)
Inputs: temp (required), target (required), brightness.
toggleA
Toggle the power state of one or more WiZ bulbs (reads current state first)
Inputs: target (required).
turn_offB
Turn off one or more WiZ bulbs
Inputs: target (required).
turn_onC
Turn on one or more WiZ bulbs
Inputs: target (required), brightness.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: power (turn_on/turn_off/toggle), color, temperature, scenes, and status are all separate concerns. The only mild overlap is discover_lights (network scan) vs list_lights (registry lookup), but descriptions distinguish them well.
Every tool follows a consistent snake_case verb_noun pattern (discover_lights, set_color, get_status, turn_on), with predictable verbs for each operation type.
10 tools is well-scoped for a smart bulb controller, with each tool earning its place across discovery, listing, power, color, scenes, and status.
Coverage is strong: discovery, power on/off/toggle, color, temperature, scenes, and status. The notable gap is a set_brightness tool — brightness is readable via get_status but not writable, which is a core lighting capability.
Maintenance
Related MCP Connectors
Yeelight device discovery, state, control, and scene execution.
MCP server for Yoto: manage cards, tracks, icons and family devices from any MCP client.
Find MCP servers for ESP32, Arduino, 3D printers, Home Assistant, cameras and other hardware.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for controlling LIFX smart lights, enabling AI assistants to manage power, color, brightness, effects, and scenes.MIT
- AlicenseAqualityDmaintenanceMCP server for controlling Elgato Key Lights. Enables turning lights on/off, adjusting brightness and color temperature, applying presets, and triggering effects via Claude.13Apache 2.0
- AlicenseAqualityDmaintenanceMCP server that enables AI agents to control Twinkly lights through natural language, supporting operations like on/off, color, brightness, and effects.1413 npmISC
- AlicenseAqualityDmaintenanceMCP server for controlling Wyze smart home devices (plugs, switches, thermostats, air purifiers) via Claude Desktop or Home Assistant.7MIT