Skip to main content
Glama
tomnz

pixelblaze

by tomnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to pixelblaze

No user-submitted related servers found.

    Related Servers

    • hue-mcp

      mdlopezme
      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

    • pixoo-mcp-server

      cyanheads
      A
      license
      A
      quality
      A
      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
      84 npm
      10
      Apache 2.0
    • display-mcp by luscoma

      display-mcpofficial

      luscoma
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to compose, validate, preview, and push JSON documents to an e-paper display powered by an ESP32, with status tracking of the panel's fetch and rendering.
      -

    • tl-draw-mcp

      Siddharth11Roy
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables Claude to draw on a live tldraw canvas from prompts, with real-time visualization in a browser. Provides tools for creating, updating, deleting shapes and retrieving canvas state.
      15
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 issues

    Resources