hue-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_homeB | Rooms and zones, with their lights' current state and their scenes. |
| set_lightsB | Turn lights on or off, or change their brightness, color or white tone. Setting brightness, a color or a white tone also turns the lights on. |
| set_powerA | Light the target with about this many watts in total, e.g. "use 20 watts". Every light in the target is turned on at the same brightness; colors and white tones stay as they are. |
| activate_sceneC | Activate a saved scene. |
| create_sceneB | Save the current look of a room or zone's lights as a new scene. |
| set_effectA | Start a light effect, or stop effects with "none". candle, fire, prism, sparkle, opal, glisten, underwater, cosmos, sunbeam and enchant loop until stopped. sunrise and sunset brighten or dim gradually over duration_minutes (wake-up light, falling asleep). Lights that don't support the effect are skipped. |
| set_timerA | Do something after a delay, e.g. turn the bedroom off in 30 minutes. The timer runs on the bridge, so it fires even after this conversation ends. |
| list_timersB | Timers set with set_timer that haven't fired yet. |
| cancel_timerB | Cancel a timer from list_timers. |
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 9 tools
Most tools target distinct actions or resources: get_home is read-only, scene tools, timer tools, and set_effect are clearly separate. The main overlap is set_lights vs set_power, since both affect brightness, but set_power uses total wattage and preserves color, making misselection unlikely though possible.
All nine tools use a consistent snake_case verb_noun pattern (get_home, set_lights, activate_scene, list_timers, etc.). The convention is predictable and easy to follow.
Nine tools is well within the ideal 3-15 range for a smart-lighting controller. Each tool earns its place by covering state read, light control, power, scenes, effects, and timers.
Core Hue workflows are covered: state inspection, on/off, brightness/color/white tone, wattage, scenes, effects, and timers. Minor gaps include no delete/update for scenes and no update for timers, though agents can work around by cancelling and recreating.