HueMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUE_TIMEOUT | No | Per-request timeout in seconds | 10 |
| HUE_VERIFY_TLS | No | 0 skip, 1 system trust, or path to CA bundle | 0 |
| HUE_BRIDGE_HOST | Yes | Hostname or IP of the bridge | |
| HUE_APPLICATION_KEY | Yes | Application key from the bridge |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_lightsA | List every light on the bridge with on/off state, brightness, colour, and owner.
|
| list_roomsA | List rooms with their |
| list_zonesA | List zones with their Zones differ from rooms: a light belongs to exactly one room but can be in many zones (e.g. a "Downstairs" zone spanning Kitchen + Living room). |
| list_scenesA | List scenes. If |
| get_resourceA | Generic escape hatch — fetch a Hue resource by type, optionally by id.
|
| set_lightA | Update one light. Pass only the attributes you want to change. Use
|
| set_groupA | Control all lights in a room or zone at once via its Get this id from |
| activate_sceneA | Recall a scene — applies its stored light states to its target group.
|
| identify_lightA | Make a light breathe (briefly pulse) so you can physically locate it. |
| bridge_infoA | Return basic bridge identity (name, id, software version, time-zone). |
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
Each tool has a clear, distinct purpose: listing resources, controlling lights individually or by group, activating scenes, identifying devices, and fetching bridge info. The generic get_resource is explicitly an escape hatch for unmapped resources.
All tool names follow a consistent verb_noun pattern (e.g., list_lights, set_light, activate_scene) using lowercase and underscores. No mixed conventions or vague verbs.
10 tools is well-scoped for a Hue bridge server, covering key operations (listing, setting, scenes, identification) without unnecessary bloat or missing essentials.
Covers core lighting control well with CRUD-like operations but lacks dedicated tools for sensors or scene creation. The generic get_resource mitigates minor gaps, and scene management relies on the app, which is reasonable.