Skip to main content
Glama
Hue MCP Server
by tebinraouf

Hue MCP Server

Control Philips Hue lights through VS Code Copilot or Claude Desktop using the Model Context Protocol (MCP).

Quick Setup

1. Prerequisites

2. Install Dependencies

uv sync

3. Configure Your Bridge IP

Edit .env file:

HUE_BRIDGE_IP=192.168.1.XXX  # Replace with your bridge IP

4. First-Time Authentication

Press the physical button on your Hue Bridge, then run:

uv run python -c "from phue import Bridge; Bridge('YOUR_BRIDGE_IP')"

Related MCP server: Philips Hue MCP Server

Usage

For VS Code Copilot

Add to your VS Code MCP configuration file (mcp.json):

Location: ~/Library/Application Support/Code/User/mcp.json (macOS)

{
  "mcpServers": {
    "custom-hue": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "__PATH__",
        "python",
        "__PATH_TO_main.py__"
      ],
      "env": {
        "HUE_BRIDGE_IP": "192.168.x.x"
      }
    }
  }
}

Note: Replace the paths with your actual project path and update HUE_BRIDGE_IP with your bridge IP.

After adding the configuration, reload VS Code and use Copilot:

  • "Turn on the corner light and set it to blue"

  • "List all my lights"

  • "Turn off all lights"

For Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "hue-lights": {
      "command": "uv",
      "args": ["run", "/FULL/PATH/TO/custom-hue/main.py"],
      "env": {
        "HUE_BRIDGE_IP": "192.168.1.XXX"
      }
    }
  }
}

Available Tools

  • change_hue_light - Control individual lights (brightness, hue, saturation, on/off)

  • list_hue_lights - List all available lights on your Hue Bridge

Available Tools

2 tools
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

Inputs: light_id (required), brightness, hue, saturation, +1 more. Returns: result

list_hue_lightsA

List all available Philips Hue lights.

Returns: A formatted list of all lights with their IDs, names, and current states

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers