Skip to main content
Glama
cyanheads

pixoo-mcp-server

by cyanheads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pixoo-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-divoom-lan by DivoomDevelop

      mcp-divoom-lanofficial

      DivoomDevelop
      A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to control Divoom LAN devices, including watchface management, brightness adjustment, and screen control through natural language.
      18
      34 npm
      7
      MIT

    • pixelblaze

      tomnz
      F
      license
      A
      quality
      D
      maintenance
      Enables Claude to create, update, and manage LED patterns on a PixelBlaze controller, including setting brightness and reading device info, through a set of tools that interact with the device's API.
      14
      -

    • n3 MCP server

      MelvinTo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to directly control a Mirabox Stream Dock N3 via tools for key/screen updates, brightness, power, event listening, and layout management.
      MIT

    • pixel-mcp

      ehm-93
      A
      license
      B
      quality
      D
      maintenance
      Enables LLMs to create and edit pixel art reliably with support for layers, frames, symmetry, and various drawing tools.
      70
      MIT No Attribution
    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/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct content type or device operation: scene composition, text rendering, image pushing, HTML rendering, overlay management, device control, discovery, and design guidance. Descriptions explicitly cross-reference (e.g., 'For text-only display use pixoo_display_text'), leaving little room for misselection.

    Naming Consistency5/5

    All tools share the pixoo_ prefix and use snake_case with a predictable verb_noun structure (compose_scene, push_image, control_device, etc.), with only design_brief being a minor noun-phrase variant. The pattern is consistent throughout.

    Tool Count5/5

    Eight tools is well-suited to the domain, covering setup, control, multiple rendering paths, and guidance without bloat. Each tool appears to earn its place, and the set is neither too thin nor too heavy.

    Completeness4/5

    The surface covers discovery, device state control, text, overlay, image, HTML, and scene composition, plus a design brief. A minor gap is the lack of an explicit way to push a composed scene to the display (compose_scene only mentions returning an image), though other tools may cover workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources