About AI HueBot
AI HueBot is an MCP server that lets AI clients control Philips Hue lights using mood descriptions or direct settings. It saves lighting presets and uses ratings and feedback to guide future vibe choices.
Key features
- 01Set light colors and brightness by mood
- 02Control individual or all lights
- 03Activate Hue scenes by name
- 04Save and reapply lighting vibes
- 05Rate vibes and review feedback
- 06Access top-rated favorites
Use cases
- 01Set warm lighting for an evening
- 02Adjust one room's lights directly
- 03Reuse a saved lighting setup
- 04Find preferred vibes from past ratings
MCP support
Exposes Philips Hue authorization, light control, scene, vibe, and feedback tools to MCP clients. It connects to the Hue Remote API using OAuth 2.0.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
15Saved tool list · updated 3w ago
This tool takes no parameters.
Details
From the project READMEAI HueBot
Control your Philips Hue lights with AI. Set vibes, save favorites, and let it learn your preferences over time.
An MCP server that connects any AI client (Claude, etc.) to your Hue lights. Just describe the mood you want.
Features
- Vibe mode -- say "cozy evening" or "deep focus" and the AI picks colors and brightness for every light
- Saved vibes -- every vibe is auto-saved and can be re-applied later
- Ratings & feedback -- rate vibes 1-10 so the AI learns what you like
- Favorites -- quickly access your top-rated vibes
- Individual & bulk control -- set any light or all lights at once
- Scene activation -- trigger any Hue scene by name
- Smart hints -- gently introduces the feedback system to new users
- Zero config auth -- built-in OAuth credentials, just authorize in your browser once
Quick Start
npx ai-huebot
That's it. Add it to your AI client (see below), then just ask:
"Set a cozy evening vibe"
"Make the bedroom warm orange at 40%"
"Rate that vibe 9 out of 10"
"Apply my highest rated vibe"
Setup
Claude Code
claude mcp add ai-huebot -- npx ai-huebot
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"ai-huebot": {
"command": "npx",
"args": ["ai-huebot"]
}
}
}
Any MCP Client
- Command:
npx - Args:
["ai-huebot"] - Transport: stdio
First Run
Call the hue_auth tool from your AI client. It opens your browser to authorize with Philips Hue. Tokens are saved to ~/.ai-huebot/tokens.json and refresh automatically.
Tools
| Tool | Description |
|---|---|
hue_auth | Authorize with Philips Hue (browser OAuth) |
list_lights | List all lights with current state |
set_light | Control a single light (on/off, brightness, color) |
set_all_lights | Set all lights to the same state |
set_scene | Activate a Hue scene by name |
set_vibe | Describe a mood -- AI picks colors for each light (auto-saves) |
save_vibe | Manually save a light configuration as a named vibe |
list_saved_vibes | List all saved vibes |
apply_saved_vibe | Re-apply a saved vibe |
delete_saved_vibe | Delete a saved vibe |
rate_vibe | Rate a vibe (1-10) and/or leave text feedback |
get_vibe_feedback | View all feedback, filterable by rating |
get_favorites | Get your top-rated vibes (rating >= 7) |
get_user_hint | Get a one-time hint about the feedback system |
acknowledge_hint | Dismiss the hint permanently |
How It Works
Auth: OAuth 2.0 against the Hue Remote API (CLIP v2). Built-in credentials work out of the box -- or set HUE_CLIENT_ID, HUE_CLIENT_SECRET, and HUE_CALLBACK_URL env vars to use your own.
Vibes: When you describe a vibe, the AI chooses hex colors and brightness for each light. The configuration is automatically saved to ~/.ai-huebot/saved-vibes/ as JSON so you can re-apply it anytime.
Feedback loop: Rate vibes and leave feedback. The AI uses this history to suggest vibes you'll like and avoid ones you didn't. Favorites (rating >= 7) are surfaced on request.
Development
git clone https://github.com/EthanSK/ai-huebot-mcp.git
cd ai-huebot-mcp
npm install
npm run build # compile TypeScript
npm run dev # run with tsx (auto-reload)
Troubleshooting
-
403 on CLIP v2 API -- CLIP v2 requires a
hue-application-keyheader containing a whitelisted bridge username. Thehue_authflow creates this automatically, but if the stored username is lost or invalid, v2 calls will return 403. The server automatically falls back to the v1 API in this case. To fix permanently, re-runhue_authto re-establish the bridge link. -
Auth token expiry -- Access tokens last 7 days and auto-refresh using the stored refresh token. If refresh fails (e.g. revoked access), re-run
hue_authto re-authorize. -
Bridge not responding -- Make sure your Hue bridge is powered on and on the same network as your machine. The bridge's local IP can change if your router reassigns it -- check the Hue app for the current IP.
-
MCP server not loading in Claude Code -- MCP servers initialize at session start. If AI HueBot doesn't appear, run
/reload-pluginsor restart the Claude Code session. Run/doctorto check for configuration errors.
License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.