wiz-light-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_lightsA | Scan the local network for WiZ smart bulbs via UDP broadcast |
| list_lightsA | List all previously discovered WiZ bulbs (from the in-memory registry) |
| turn_onC | Turn on one or more WiZ bulbs |
| turn_offB | Turn off one or more WiZ bulbs |
| toggleA | Toggle the power state of one or more WiZ bulbs (reads current state first) |
| set_colorB | Set the RGB color of one or more WiZ bulbs |
| set_temperatureA | Set the color temperature of one or more WiZ bulbs (warm to cool white) |
| set_sceneB | Activate a WiZ scene by name or ID on one or more bulbs |
| get_statusA | Get the current state of a WiZ bulb (power, brightness, color, scene, etc.) |
| list_scenesA | List all 32 available WiZ light scenes with their IDs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.