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
      C
      maintenance
      Enables AI clients to control Divoom LAN devices, including watchface management, brightness adjustment, and screen control through natural language.
      18
      41 npm
      4
      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
      C
      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.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: discovery, device state control, styled text, layered scenes, image push, overlay text, and design guidance. The two text-related tools (display_text vs overlay_text) and display_text vs compose_scene are explicitly differentiated in their descriptions, which cross-reference each other and clarify when to use which.

    Naming Consistency5/5

    All tools share the pixoo_ prefix with a consistent snake_case verb_noun pattern (discover_devices, display_text, compose_scene, push_image, control_device, overlay_text). design_brief is the only slight deviation but remains readable and follows the same casing convention.

    Tool Count5/5

    Seven tools is well-scoped for a device-control server, with each tool earning its place across discovery, control, rendering, and guidance. No obvious redundancy or bloat.

    Completeness4/5

    The surface covers the full lifecycle: discover device, read/change state, render text/scenes/images, set overlays, and get design guidance before authoring. Minor gaps like a dedicated clear/reset display or saved-scene management exist but can be worked around via control_device and overlay clear modes.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources