HueMCP
An MCP server that lets Claude (or any MCP client) discover and control a Philips Hue bridge over its local CLIP v2 HTTP API. No cloud account needed — all traffic is LAN-local to your bridge.
Tool surface
| Tool | Purpose |
|---|---|
list_lights() |
Every light with on/off, brightness, colour, owner device |
list_rooms() |
Rooms with their grouped_light_id and member devices |
list_zones() |
Zones with their grouped_light_id and member lights |
list_scenes(group_id=None) |
Scenes, optionally filtered to one room/zone |
set_light(light_id, on?, brightness?, color_temp_mirek?, color_xy?, effect?, gradient_points?, gradient_mode?, timed_effect?, timed_effect_duration_ms?, transition_ms?) |
Update one light |
set_group(grouped_light_id, on?, brightness?, color_temp_mirek?, color_xy?, transition_ms?) |
Update all lights in a room or zone |
activate_scene(scene_id, brightness?, transition_ms?, action="active") |
Recall a scene |
identify_light(light_id) |
Briefly pulse a light to locate it |
bridge_info() |
Basic identity of the bridge |
get_resource(rtype, rid=None) |
Generic escape hatch — raw bridge payload for any resource type |
brightness is a percent (0–100). color_temp_mirek is a CIE mired value
(typical range 153–500 ≈ 6500K–2000K — the per-light valid range is reported
by list_lights()). color_xy is [x, y] in CIE 1931 space, clamped to the
light's gamut.
list_lights() also reports per-light capability: effects.available
(e.g. candle, fire, prism, sparkle, opal, glisten), timed_effects.available
(sunrise, sunset), and — for gradient lightstrips — a gradient block
with points_capable, pixel_count, and mode_values. Pass matching values
to set_light to drive them: effect="candle", gradient_points=[[x,y], ...],
timed_effect="sunrise", etc.
Requirements
- Python 3.10+
- A Hue bridge reachable on your LAN
- An application key — generated by pressing the link button and POSTing to
/api(see "Bridge-side setup" below) - An MCP-capable client — these instructions assume Claude Code
Install
git clone <your-fork-url> HueMCP
cd HueMCP
python3 -m venv .venv
.venv/bin/pip install -e .
cp .env.example .env
# edit .env to set HUE_BRIDGE_HOST and HUE_APPLICATION_KEY
Smoke test:
.venv/bin/python scripts/smoke_test.py
Register with Claude Code (user scope, available in every project):
claude mcp add huemcp /absolute/path/to/HueMCP/.venv/bin/huemcp -s user
Bridge-side setup
-
Find your bridge's IP at https://discovery.meethue.com or in the Hue app (Settings → My Hue System).
-
Press the bridge's physical link button.
-
Within 30 seconds, request an application key:
curl -sk -X POST https://<bridge-ip>/api \ -H 'Content-Type: application/json' \ -d '{"devicetype":"huemcp#'"$(hostname)"'", "generateclientkey":true}'
Copy the
usernamevalue from the response intoHUE_APPLICATION_KEY.
TLS
The bridge presents a self-signed certificate signed by the Philips Hue root CA.
By default HUE_VERIFY_TLS=0 and the client skips verification — appropriate
for a LAN-local device. To verify properly, install the Hue root CA into your
trust store and set HUE_VERIFY_TLS=1, or pin a CA bundle by setting
HUE_VERIFY_TLS=/path/to/ca.pem.
Configuration reference
| Variable | Default | Purpose |
|---|---|---|
HUE_BRIDGE_HOST |
(required) | Hostname or IP of the bridge |
HUE_APPLICATION_KEY |
(required) | Application key from the bridge |
HUE_VERIFY_TLS |
0 |
0 skip, 1 system trust, or path to CA bundle |
HUE_TIMEOUT |
10 |
Per-request timeout in seconds |
License
MIT — see LICENSE.
Metadata
Release files for huemcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| huemcp-0.1.0.tar.gz | 9.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| huemcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.6 kB
Release files / huemcp-0.1.0.tar.gz
| Download URL | huemcp-0.1.0.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21b1ec6236a9018e1fea0c49d38e4bc795384ccd10fad1cad3c88001ca31549b
|
|
BLAKE2b-256 checksum How to use checksums |
689b828ea101006339458111b3d66d1ea0032d71242af43d5b7ed2035e020d88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / huemcp-0.1.0-py3-none-any.whl
| Download URL | huemcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
080e0130e139d1810e56faa2567729a6fa6a05449ad6b03af9041ab036052a0d
|
|
BLAKE2b-256 checksum How to use checksums |
843a6e6c567035e4904d8694a344797c54fe318d63e2852dcd3eb860d15a77f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for huemcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.