OpenRGB Status Light MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENRGB_PORT | No | Force the OpenRGB SDK server port instead of auto-discovering it. | |
| OPENRGB_DEVICE | No | Select the OpenRGB device by a name fragment. | |
| OPENRGB_MCP_STATE | No | Path to the state cache file. | |
| OPENRGB_MCP_CONFIG | No | Path to the configuration file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
OpenRGB status lamp. Use set_state to mirror the conversation state on the host LEDs, set_progress / set_quota to turn the LED count into a progress or remaining-budget bar, and list_devices to learn how many LEDs the device has.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | Read the OpenRGB device inventory: devices, zones, modes and how many LEDs each device has. The LED count is the length of a progress bar. |
| statusA | Report the current lamp state: state, LED count, device, SDK port, whether the animation is running, active progress/quota and the last error. |
| set_stateA | Switch the host LEDs to a conversation state. state: idle | thinking | working | waiting | done | error | off (aliases such as complete/failed/ask are accepted). All animations are slow, continuous fades - the lamp never strobes. thinking = blue breathing, working = cyan breathing, waiting = amber fade, done = solid green, error = red fade, idle = dim blue breathing, off = lights out. detail is a short note kept in the status output. animate: set to false to freeze the effect. |
| set_progressA | Turn the LED strip into a progress bar: the completed part is lit, the rest is dark. Pass percent (0-100) or both done and total. color overrides the bar colour (#RRGGBB). state selects the palette entry (default 'working'). |
| set_quotaB | Show how much of a budget is left using the LED count: the bar is filled proportionally to remaining/total and coloured green above 50%, amber between 20% and 50%, red at 20% or less. Use it for token budgets, API balance, remaining steps and similar. |
| set_colorA | Paint every LED with one colour (#RRGGBB). brightness (0-1) scales it. |
| set_ledsA | Set an explicit colour per LED (#RRGGBB). The list length must equal the device's LED count - query it with list_devices. Use it for gradients and patterns. |
| set_effectA | Hand the LEDs over to one of the device's own effects (for example 'Static', 'Breathing', 'Wave' - the available names depend on the device and are listed by list_devices). This stops the status animation; call set_state again to resume it. |
| restoreA | Restore the colours the device had before this server took over and stop the status animation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| status-lamp | Instructions for mirroring the conversation state onto the host LEDs. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| OpenRGB lamp status | JSON snapshot of the lamp: state, LED count, device, animation, progress/quota. |
| OpenRGB device inventory | JSON inventory of the OpenRGB devices, their zones, modes and LED counts. |
TDQS
Scored across 9 tools
Most tools target clearly different outputs: set_state for semantic lamp states, set_color for a uniform fill, set_leds for per-LED patterns, set_effect for native device effects, and status/list_devices/restore for reads and cleanup. The main overlap is set_progress vs set_quota, which both render a bar and differ only by colour thresholds, and set_state vs set_effect, which both animate the LEDs; the descriptions do clarify the boundary, so confusion is limited rather than pervasive.
Seven of nine tools follow a clean verb_noun pattern (set_state, set_color, set_leds, set_progress, set_quota, set_effect, list_devices). The exceptions are bare 'status' (noun-only) and 'restore' (verb-only), which are readable but break the pattern slightly.
Nine tools is well within the ideal range and each earns its place: two read tools, five distinct LED-control modes, plus a status read and a restore/cleanup path. Nothing feels padded or redundant enough to remove.
The surface covers the full lifecycle of taking over the lamp: inventory, state animation, solid colour, per-LED patterns, progress/quota bars, native effects, status reporting, and restoring the prior colours. Minor gaps remain, such as a global brightness control independent of set_color or a way to persist/query a saved state across sessions.