Hue MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUE_BRIDGE_IP | Yes | The IP address of your Hue Bridge (find it in the Hue app or at https://discovery.meethue.com/) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| change_hue_lightA | Change the state of a Philips Hue light. Args: light_id: The ID of the light to control (1-based index) brightness: Brightness level (0-254), where 0 is minimum and 254 is maximum hue: Hue color value (0-65535), where 0 and 65535 are red, 25500 is green, and 46920 is blue saturation: Color saturation (0-254), where 0 is white and 254 is most saturated on: Turn the light on (True) or off (False) Returns: A message indicating the result of the operation |
| list_hue_lightsA | List all available Philips Hue lights. Returns: A formatted list of all lights with their IDs, names, and current states |
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 2 tools
The two tools have completely distinct purposes with no overlap: one lists lights (read-only) while the other controls light states (write operation). An agent would never confuse these tools as they operate on different aspects of the Hue system.
Both tools follow a consistent verb_noun pattern with 'hue_light(s)' as the common noun component. 'list_hue_lights' and 'change_hue_light' maintain perfect naming consistency throughout the toolset.
With only 2 tools, this server feels severely underpowered for controlling a Philips Hue lighting system. A proper Hue interface would need tools for scenes, groups, schedules, bridge configuration, and more comprehensive light management beyond just listing and changing individual lights.
The tool surface is severely incomplete for Hue light control. Missing essential operations include: creating/deleting lights, managing scenes or groups, adjusting transition times, setting color temperatures, configuring bridge settings, and error handling for unavailable lights. Agents will hit dead ends trying to perform basic Hue workflows.