AI HueBot
Allows AI agents to control Philips Hue lights, including setting moods/vibes, adjusting individual or all lights, activating scenes, and managing saved vibes with ratings and feedback.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AI HueBotset a calm blue vibe for the bedroom"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AI 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
Related MCP server: LIFX MCP Server
Quick Start
npx ai-huebotThat'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-huebotClaude 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:
npxArgs:
["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 |
| Authorize with Philips Hue (browser OAuth) |
| List all lights with current state |
| Control a single light (on/off, brightness, color) |
| Set all lights to the same state |
| Activate a Hue scene by name |
| Describe a mood -- AI picks colors for each light (auto-saves) |
| Manually save a light configuration as a named vibe |
| List all saved vibes |
| Re-apply a saved vibe |
| Delete a saved vibe |
| Rate a vibe (1-10) and/or leave text feedback |
| View all feedback, filterable by rating |
| Get your top-rated vibes (rating >= 7) |
| Get a one-time hint about the feedback system |
| 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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/EthanSK/ai-huebot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server