AI HueBot

@EthanSK

About AI HueBot

Control your Philips Hue lights with AI. MCP server for setting vibes, saving favorites, and learning your lighting preferences.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "hue-vibes-mcp": {
      "command": "npx",
      "args": [
        "ai-huebot"
      ]
    }
  }
}

Tools

Start the Philips Hue OAuth authorization flow. Opens a browser window to authorize access to your Hue lights. Only needed on first use or when tokens expire.

List all Philips Hue lights with their current state including on/off, brightness, and color.

Set a specific Hue light's state. You can control on/off, brightness (0-100), and color (hex string like #FF0000 or xy coordinates).

Set all Hue lights to the same state. You can control on/off, brightness, and color.

Activate a Hue scene by name. Lists available scenes if the exact name is not found.

Set a vibe across your lights. Provide a vibe description and an array of light settings that match the vibe. Claude should determine appropriate colors and brightness for each light based on the vibe description.

Save the current light state as a named vibe. Captures a snapshot of specified lights with their colors and brightness so it can be re-applied later.

List all previously saved vibes. Shows names, descriptions, and light configurations.

Apply a previously saved vibe by name. Restores the light configuration that was saved.

Delete a previously saved vibe by name.

Rate a vibe and/or leave feedback. At least one of rating or feedback must be provided. Use the vibe name from saved vibes.

Retrieve all vibe feedback entries. Optionally filter by minimum rating or sort by rating. Useful for understanding user preferences.

Get top-rated vibes (rating >= 7 by default). Use this to suggest vibes the user has enjoyed before.

Get a hint message about the feedback system for the user. Returns a hint only if the user hasn't been told about the feedback system yet. Relay the hint text to the user if one is returned.

Mark the feedback system hint as shown so it won't be displayed again.

Overview

What is AI HueBot?

AI HueBot is an MCP (Model Context Protocol) server that connects any AI client (e.g., Claude) to your Philips Hue lights. It lets you control lights by describing moods, auto‑saves vibes, and learns your preferences through ratings and feedback. Designed for anyone who wants to set lighting scenes using natural language.

How to use AI HueBot?

Run npx ai-huebot to start the server, then add it to your MCP client (Claude Code, Claude Desktop, etc.). On first run, call the hue_auth tool to authorize with Philips Hue via browser OAuth. Then simply ask your AI to set a vibe, control lights, rate a vibe, or apply favorites.

Key features of AI HueBot

Vibe mode – describe a mood and the AI picks colors and brightness per light
Auto‑saved vibes – every vibe is saved and can be re‑applied later
Ratings & feedback – rate vibes 1–10 so the AI learns your taste
Favorites – quickly access top‑rated vibes (rating ≥ 7)
Individual & bulk control – set any light or all lights at once
Zero‑config auth – built‑in OAuth credentials; just authorize once in your browser

Use cases of AI HueBot

Set a “cozy evening” or “deep focus” mood without touching your phone or app
Create and re‑apply personalized lighting presets for different activities
Let the AI suggest vibes based on your past ratings and feedback
Activate any existing Hue scene by name using voice or text commands

FAQ from AI HueBot

How does authentication work?

AI HueBot uses OAuth 2.0 against the Philips Hue Remote API (CLIP v2). Built‑in credentials work out of the box – you just authorize once in your browser. Tokens are saved to ~/.ai-huebot/tokens.json and auto‑refresh every 7 days.

Where are vibes and feedback stored?

Saved vibes are stored as JSON files in ~/.ai-huebot/saved-vibes/. Feedback data is stored alongside those files. All data remains on your local machine.

What if my Hue bridge stops responding?

Make sure the 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.

What happens if the OAuth token expires?

Access tokens last 7 days and auto‑refresh using the stored refresh token. If the refresh fails (e.g., revoked access), re‑run the hue_auth tool to re‑authorize.

What transport does AI HueBot use?

The server communicates over stdio (standard input/output). You configure it in your MCP client with command npx and args ["ai-huebot"].

Frequently asked questions

How does authentication work?

AI HueBot uses OAuth 2.0 against the Philips Hue Remote API (CLIP v2). Built‑in credentials work out of the box – you just authorize once in your browser. Tokens are saved to `~/.ai-huebot/tokens.json` and auto‑refresh every 7 days.

Where are vibes and feedback stored?

Saved vibes are stored as JSON files in `~/.ai-huebot/saved-vibes/`. Feedback data is stored alongside those files. All data remains on your local machine.

What if my Hue bridge stops responding?

Make sure the 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.

What happens if the OAuth token expires?

Access tokens last 7 days and auto‑refresh using the stored refresh token. If the refresh fails (e.g., revoked access), re‑run the `hue_auth` tool to re‑authorize.

What transport does AI HueBot use?

The server communicates over **stdio** (standard input/output). You configure it in your MCP client with command `npx` and args `["ai-huebot"]`.

Comments

Basic information

More Other MCP servers

Mcp

browsermcp

Browser MCP is a Model Context Provider (MCP) server that allows AI applications to control your browser

6.8K

Reactive Resume

amruthpillai

A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

39.5K