airglow
Allows controlling Philips Hue lights, including setting colors, brightness, effects, and status-based animations, with session hooks for Claude Code.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
. * . * . * . * . * . * .
* *
. _________________________ .
* | | *
. | * . * . * . * . * . | .
* | . A I R G L O W . | *
. | * . * . * . * . * . | .
* | . * . * . * . * . | *
. |_________________________| .
* *
. * . * . * . .
* . * . * . * . * . * . * .airglow
Watch Claude think. A Philips Hue MCP server + Claude Code hooks that animate your lights in real time based on what Claude is doing — cyan while thinking, magenta while working, green on success, red on permission prompts. Every session, every tool call, every moment of focus: visible. Works even when your screen is locked or off — glance at the light to know if Claude needs your attention.
Prerequisites
Node.js 18 or later
Philips Hue bridge (gen 2+) on your local network
At least one color-capable Hue bulb
Related MCP server: Hue MCP Server
Install
npm installSetup
The setup tool handles everything. Call it from Claude at any point — it checks your config and tells you exactly what to do next.
1. Add to Claude Code
Drop this into ~/.claude/settings.json:
{
"mcpServers": {
"hue": {
"command": "node",
"args": ["/path/to/airglow/index.js"]
}
}
}2. Run guided setup
setup()The tool will auto-discover your bridge, walk you through registering an API key (press the link button, call create_user), then list your lights and suggest one for animations — matched by name. Finish with one call:
setup({ default_group: 0, hook_light_id: 6 })This saves everything to .env and returns a ready-to-paste hook block for your project's .claude/settings.json.
Environment variables
Variable | Default | Description |
| — | Bridge IP address |
| — | API key (from |
|
| Group ID for |
| — | Light ID for session animations |
|
| Brightness cap, 0–100% |
Copy .env.example to .env to configure manually, or let setup() write these for you.
Claude Code Session Hooks
thinking working prompt
~~~~~~~~~~~~ ~~~~~~~~~~ ~~~~~~~~~~~~~~
~ CYAN pulse ~ ~ MAGENTA ~ ~ RED pulse ~
~ slow breathe~ ~ pulse ~ ~ 30s then ~
~~~~~~~~~~~~~ ~~ ~~~~~ ~~~ ~ idle ~
~~~~~~~~~~~~~~hue-status.js animates a single light based on Claude Code session events. Every hook invocation kills the previous pulse and starts fresh — no orphaned processes, no stuck colors.
Event | Color | Behavior |
User submits prompt | cyan | pulse (thinking) |
Tool starts | magenta | pulse (working) |
Tool ends | cyan | pulse (thinking) |
Plan approved | green | solid flash, then resumes |
Permission prompt | red | pulse, 30s auto-expire → idle |
Session ends | — | restores pre-session state |
The pre-session light state is saved on the first prompt of each session and restored when the session stops.
Hook configuration
Generated automatically by setup(). To configure manually, add to your project's .claude/settings.json:
{
"hooks": {
"UserPromptSubmit": [
{ "hooks": [{ "type": "command", "command": "node /path/to/airglow/hue-status.js thinking" }] }
],
"PreToolUse": [
{ "hooks": [{ "type": "command", "command": "node /path/to/airglow/hue-status.js working" }] }
],
"PostToolUse": [
{ "matcher": "exit_plan_mode", "hooks": [{ "type": "command", "command": "node /path/to/airglow/hue-status.js success" }] },
{ "hooks": [{ "type": "command", "command": "node /path/to/airglow/hue-status.js thinking" }] }
],
"Notification": [
{ "matcher": "permission_prompt", "hooks": [{ "type": "command", "command": "node /path/to/airglow/hue-status.js prompt" }] }
],
"Stop": [
{ "hooks": [{ "type": "command", "command": "node /path/to/airglow/hue-status.js restore" }] }
]
}
}The light ID defaults to HUE_HOOK_LIGHT from .env. To pin a project to a specific light, pass the ID as the second argument:
node hue-status.js thinking 55To bind different projects to different lights without git conflicts, use settings.local.json (automatically gitignored by Claude Code) in each project's .claude/ directory.
Available Tools
Tool | Description |
| Guided onboarding — discovers bridge, registers API key, selects animation light, returns hook config |
| Find Hue bridges on the local network |
| Register a new API user (press the link button first) |
| List lights — filterable by room, on/off state, or color capability |
| List all groups and rooms |
| List all saved scenes |
| List motion sensors, temperature sensors, buttons, and remotes |
| List animated smart scenes — Candle, Fireplace, etc. (v2 API) |
| Control a single light — on/off, brightness (0–100%), color temp (153–500 mired), RGB, HSL, flash alert, transition time |
| Control all lights in a group simultaneously — same params as |
| Apply a native animated effect to lights — candle, fire, prism, sparkle, opal, glisten, cosmos. Pass |
| Set lights to a semantic status color |
| Activate a saved scene by ID |
| Activate an animated smart scene with optional speed control |
| Snapshot current light state as a named scene |
Status Colors
set_status maps named statuses to specific light states — great for CI pipelines, agents, or anything that has a "mood."
Status | Color | Vibe |
| warm white | nothing happening |
| soft blue | Claude is reasoning |
| bright blue | tools firing |
| amber | compiling / CI |
| purple | blocked on review |
| green | nailed it |
| teal | shipped |
| red | something broke |
| red flash | wake up |
| one breathe cycle | gentle nudge, returns to prior state |
| off | done |
set_status({ status: "thinking" })
set_status({ status: "success", group_id: 3 })
set_status({ status: "pulse_once", light_id: 6 })Dynamic Scenes
get_dynamic_scenes and activate_dynamic_scene use the Hue v2 CLIP API to access animated smart scenes. Requires gen 2 bridge with current firmware and scenes created in the Hue app.
get_dynamic_scenes()
activate_dynamic_scene({ scene_id: "uuid-from-above" })
activate_dynamic_scene({ scene_id: "uuid", speed: 0.7 }) // speed: 0.0–1.0Scene Snapshots
create_scene captures exactly what your lights look like right now as a named scene you can recall anytime:
create_scene({ name: "Evening Work" }) // captures HUE_DEFAULT_GROUP
create_scene({ name: "Office Focus", group_id: 3 }) // specific room
create_scene({ name: "Desk Only", light_ids: [6, 55] }) // specific lightsReturns a scene ID ready for activate_scene.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Create projects, nodes, and tasks in UluP Spaces by conversation with Claude.
Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables control of Philips Hue lights through Claude and other LLM interfaces using the OpenHue CLI.610MIT
- FlicenseAqualityDmaintenanceEnables 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-
- AlicenseAqualityDmaintenanceEnables control of Philips Hue lights via Bluetooth LE directly from Claude, without requiring a Hue Bridge or internet connection.81MIT
- FlicenseNot gradedqualityCmaintenanceA production-ready Model Context Protocol (MCP) server that enables Claude to control Philips Hue lights through natural language commands.-