Skip to main content
Glama

Related Servers

Alternatives to pixelblaze

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to control Philips Hue lights through a Hue Bridge on the local network, handling plain-language requests for on/off, brightness, color, scenes, looping effects, and whole-room power budgets. Fades and timers run on the bridge itself, and no Hue cloud account is required.
      9
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude to control Tuya and Smart Life Wi-Fi bulbs over the local network without cloud dependence, including power, brightness, color, presets, scenes, zones, and delayed or ambient lighting changes.
      10
      43 PyPI
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables programmatic control of Divoom Pixoo LED matrices to display layered pixel art, animations, and hardware-rendered scrolling text. Users can compose complex visual scenes, push images, and manage device settings like brightness and channels through an LLM.
      8
      213 npm
      11
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read and safely edit Yoto MYO playlists and interactive cards by title, with every write planned first as a diff, then backed up, applied, and verified. Also compiles and simulates interactive story graphs, generates spoken prompts locally, and draws pixel-exact 16×16 icons.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to control Bambu Lab printers over the LAN, including status and AMS reads, job-based slicing, uploading and printing, print monitoring, and guarded control commands. Long-running operations are handled by a background job manager with polling, persistence, dry-run, and read-only safety modes.
      1
      MIT

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct action: documentation tools are separated by page type, and device tools cover unique operations (CRUD, controls, brightness, info) with no overlap.

    Naming Consistency5/5

    All tools follow a consistent snake_case format with the server name prefix (docs_ or pixelblaze_) followed by a verb and noun, making the purpose clear.

    Tool Count5/5

    14 tools is well-scoped for managing PixelBlaze patterns, controls, brightness, and documentation; neither too sparse nor overwhelming.

    Completeness5/5

    Covers full lifecycle of patterns (CRUD, activation), brightness, control manipulation, device info, and essential documentation references with no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues