Skip to main content
Glama
OpenHue MCP Server

OpenHue MCP Server

by lsemenenko

OpenHue MCP Server

An MCP server that enables control of Philips Hue lights through Claude and other LLM interfaces using the OpenHue CLI.

Prerequisites

Related MCP server: Philips Hue MCP Service

Bridge Setup

Before using the server, you need to set up the OpenHue CLI with your Hue Bridge:

  1. Run the setup command:

# On Linux/macOS:
docker run -v "${HOME}/.openhue:/.openhue" --rm --name=openhue -it openhue/cli setup

# On Windows (PowerShell):
docker run -v "${env:USERPROFILE}\.openhue:/.openhue" --rm --name=openhue -it openhue/cli setup
  1. Follow the on-screen instructions:

    • The CLI will search for your Hue Bridge

    • Press the link button on your Hue Bridge when prompted

    • Wait for confirmation that the setup is complete

  2. Verify the setup by listing your lights:

# On Linux/macOS:
docker run -v "${HOME}/.openhue:/.openhue" --rm --name=openhue -it openhue/cli get lights

# On Windows (PowerShell):
docker run -v "${env:USERPROFILE}\.openhue:/.openhue" --rm --name=openhue -it openhue/cli get lights

If you see your lights listed, the setup is complete and you're ready to use the MCP server.

Installation

  1. Clone the repository:

git clone <your-repo-url>
cd claude-mcp-openhue
  1. Install dependencies:

npm install
  1. Build the project:

npm run build
  1. Run the server:

npm start

Features

This server exposes the following capabilities through MCP:

Lights Control

  • List all lights or get specific light details

  • Turn lights on/off

  • Adjust brightness

  • Set colors

  • Control color temperature

Room Control

  • List all rooms or get room details

  • Control all lights in a room together

  • Set room-wide brightness and colors

Scene Management

  • List available scenes

  • Activate scenes with different modes

  • Filter scenes by room

Usage with Claude Desktop

  1. Open your Claude Desktop configuration file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  2. Add the server configuration:

{
  "mcpServers": {
    "hue": {
      "command": "node",
      "args": ["/absolute/path/to/build/index.js"]
    }
  }
}
  1. Restart Claude Desktop

  2. Look for the hammer icon to verify the server is connected

Example Commands

Once connected, you can ask Claude natural language questions like:

  • "What lights do I have in the living room?"

  • "Turn on all the lights in the kitchen"

  • "Set the bedroom lights to 50% brightness"

  • "Change the office lights to blue"

  • "Activate the 'Relaxing' scene"

  • "What scenes are available in the den?"

Available Tools

get-lights

Lists all lights or gets details for specific lights

{
  lightId?: string;  // Optional light ID or name
  room?: string;     // Optional room name filter
}

control-light

Controls individual lights

{
  target: string;    // Light ID or name
  action: "on" | "off";
  brightness?: number; // 0-100
  color?: string;     // Color name
  temperature?: number; // 153-500 Mirek
}

get-rooms

Lists all rooms or gets specific room details

{
  roomId?: string;  // Optional room ID or name
}

control-room

Controls all lights in a room

{
  target: string;    // Room ID or name
  action: "on" | "off";
  brightness?: number;
  color?: string;
  temperature?: number;
}

get-scenes

Lists available scenes

{
  room?: string;    // Optional room name filter
}

activate-scene

Activates a specific scene

{
  name: string;     // Scene name or ID
  room?: string;    // Optional room name
  mode?: "active" | "dynamic" | "static";
}

Development

Project Structure

.
├── src/
│   └── index.ts    # Main server implementation
├── build/          # Compiled JavaScript
├── package.json
├── tsconfig.json
└── README.md

Building

npm run build

Running

npm start

Troubleshooting

Server Not Connecting

  1. Check that Docker is running

  2. Verify OpenHue configuration exists

  3. Check Claude Desktop logs

  4. Try running OpenHue CLI directly

Command Failures

  1. Check OpenHue CLI permissions

  2. Verify light/room/scene names

  3. Check Docker container logs

  4. Verify Hue Bridge connectivity

License

MIT License

Contributing

  1. Fork the repository

  2. Create your feature branch

  3. Commit your changes

  4. Push to the branch

  5. Create a new Pull Request

Available Tools

6 tools
activate-sceneC

Activate a specific scene

Inputs: name (required), mode, room.

control-lightC

Control a specific Hue light

Inputs: action (required), target (required), brightness, color, +1 more.

control-roomC

Control all lights in a room

Inputs: action (required), target (required), brightness, color, +1 more.

get-lightsB

List all Hue lights or get details for a specific light

Inputs: lightId, room.

get-roomsB

List all rooms or get details for a specific room

Inputs: roomId.

get-scenesC

List all scenes or get details for specific scenes

Inputs: room.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: activate-scene targets scene activation, control-light and control-room handle light control at different granularities, and the get-* tools retrieve specific resource types. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun pattern with hyphen separation (e.g., activate-scene, control-light, get-lights). The naming is uniform across all tools, with no deviations in style or convention, ensuring predictability and readability.

    Tool Count5/5

    With 6 tools, the server is well-scoped for managing Philips Hue devices. The count is appropriate, covering core operations like control and retrieval for lights, rooms, and scenes without being overly sparse or bloated, fitting typical home automation workflows.

    Completeness4/5

    The toolset provides solid coverage for the Hue domain, including control and retrieval for lights, rooms, and scenes. A minor gap exists in missing update or delete operations for scenes or rooms, but agents can still accomplish most common tasks with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables control of Philips Hue lights through VS Code Copilot or Claude Desktop using natural language commands. Supports turning lights on/off, adjusting brightness, changing colors, and listing available lights on your Hue Bridge.
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables control of Philips Hue lights through the Model Context Protocol, providing tools for turning lights on/off, setting brightness and color, and retrieving light status.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Controls Philips Hue lights based on Claude Code session events, using color animations to indicate Claude's status (thinking, working, success, etc.).
      20 npm
      10
      Apache 2.0