Skip to main content
Glama
OpenRGB Status Light MCP

OpenRGB Status Light MCP

by sheetung

Related Servers

Alternatives to OpenRGB Status Light MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents control networked LED controllers by name—including power, brightness, segments, effects, palettes, presets, groups, scenes, and zones—with validated writes, read-back verification, and dry-run previews over stdio or HTTP.
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to inspect and safely control OBS Studio over obs-websocket v5, exposing scenes, inputs, filters, outputs and video settings as read and write tools that default to dry runs and refuse changes while live unless explicitly confirmed. It also provides Source Record and IRL readiness checks, a BRB auto-switcher, and a scene timeline log for cutting clips from VODs.
      17
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-driven control of Art-Net/sACN DMX lighting, including scenes, effects, groups, safety rules, MIDI/OSC, and Ableton Live integration through a unified command layer.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Govee smart devices, including lights, via natural language. Supports turning on/off, changing colors, adjusting brightness, and activating scenes through the Govee API or local network.
      9
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude and Codex to draw text, pixel art, images, animations and progress bars, play sounds and melodies, and show GitHub CI/inbox and weather on a BUSY Bar over USB or Wi-Fi. Also provides read-only device diagnostics and, via an optional window manager, shared display orchestration with temporary messages, timers and app switching.
      16
      1,529 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.