AI HueBot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUE_CLIENT_ID | No | Optional custom OAuth client ID for Philips Hue Remote API | |
| HUE_CALLBACK_URL | No | Optional custom OAuth callback URL for Philips Hue Remote API | |
| HUE_CLIENT_SECRET | No | Optional custom OAuth client secret for Philips Hue Remote API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hue_authA | 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. |
| hue_apiA | Make an arbitrary Philips Hue CLIP v2 API call. This gives full unrestricted access to the Hue API. The path is relative to /route/clip/v2/ (e.g. 'resource/light', 'resource/light/{id}', 'resource/scene', 'resource/grouped_light/{id}', 'resource/room', 'resource/zone', 'resource/bridge'). See https://developers.meethue.com/develop/hue-api-v2/ for full API docs. |
| list_lightsA | List all Philips Hue lights with their current state including on/off, brightness, and color. |
| set_lightB | 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_lightsA | Set all Hue lights to the same state. You can control on/off, brightness, and color. |
| set_sceneA | Activate a Hue scene by name. Lists available scenes if the exact name is not found. |
| set_vibeA | 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_vibeA | 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_saved_vibesA | List all previously saved vibes. Shows names, descriptions, and light configurations. |
| apply_saved_vibeB | Apply a previously saved vibe by name. Restores the light configuration that was saved. |
| delete_saved_vibeA | Delete a previously saved vibe by name. |
| rate_vibeA | Rate a vibe and/or leave feedback. At least one of rating or feedback must be provided. Use the vibe name from saved vibes. |
| get_vibe_feedbackA | Retrieve all vibe feedback entries. Optionally filter by minimum rating or sort by rating. Useful for understanding user preferences. |
| get_favoritesA | Get top-rated vibes (rating >= 7 by default). Use this to suggest vibes the user has enjoyed before. |
| get_user_hintA | 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. |
| acknowledge_hintA | Mark the feedback system hint as shown so it won't be displayed again. |
| get_user_profileA | Get the full user profile with light preferences, vibe history, colour preferences, and patterns. Read this before making vibe decisions to personalise recommendations. The profile is stored as markdown at ~/.ai-huebot/user-profile.md and is auto-populated over time. |
| update_user_profileA | Update a section of the user profile with new observations, preferences, or notes. Use this to record things the user tells you about their preferences, or to add evolution notes with suggestions. |
| animate_lightsA | Animate lights through a sequence of color phases. Each phase defines colors/brightness for each light, and the animation cycles through them with smooth transitions. Great for dynamic vibes like 'lava flow', 'ocean waves', 'disco', etc. The AI should generate creative phases based on the vibe description. The animation runs in the background and can be stopped with stop_animation. |
| set_effectA | Set a native Hue light effect. Supported effects: 'candle' (candle flicker), 'fire' (fireplace), 'prism' (color cycling/rainbow). Use 'no_effect' to stop. Can target a specific light or all lights. |
| stop_animationA | Stop any currently running animation or effect. Stops background phase animations started by animate_lights, and also clears any native Hue effects (candle, fire, prism) on all lights. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Most tools have distinct purposes, but there is some overlap among set_vibe, set_scene, apply_saved_vibe, and animate_lights for creating ambience, and get_favorites overlaps with get_vibe_feedback. Descriptions mostly clear up the boundaries, so only a couple of tools could be confused.
Names are consistently snake_case with verb-first patterns like list_*, set_*, get_*, save_*, and delete_*. Exceptions are hue_api and hue_auth, which lack a leading verb, but they are still descriptive and contextually appropriate.
At 21 tools, this sits in the heavy range (16-25). The expanded vibe, feedback, and profile features justify many of them, but the count feels slightly overloaded compared to typical Hue control servers.
The surface covers lighting control (states, scenes, effects, animations) plus a full vibe lifecycle with rating, feedback, favorites, hints, and user profile management. Minor gaps exist such as no dedicated room/zone management or direct saved-vibe editing, but hue_api provides an escape hatch.