Skip to main content
Glama
Sign In
pixoo-mcp-server

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

      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.
      42
      59 npm
      7
      MIT

    • Pixelorama MCP

      CyberIce2077
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to draw and edit pixel art inside a live Pixelorama editor by sending character-grid and palette commands, reading pixels back, managing layers and frames, and exporting PNGs or sprite sheets. Every operation acts on the active project and remains undoable with Ctrl+Z.
      14 npm
      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
    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 8 tools

    Disambiguation5/5

    Although several tools produce visual output, the descriptions clearly partition them: compose_scene for layered compositions, display_text for previewable text-only output, overlay_text for persistent device-native tickers, render_html for HTML pages, and push_image for file/URL images. Device control, discovery, and design guidance are also clearly separate.

    Naming Consistency5/5

    All tools use the pixoo_ prefix and snake_case with a consistent verb_noun shape: compose_scene, render_html, control_device, discover_devices, display_text, overlay_text, push_image, and design_brief. There is no mixed casing or inconsistent style.

    Tool Count5/5

    Eight tools fit the server's scope well: one discovery tool, one device-control tool, one guidance tool, and several distinct rendering/display paths. Each tool has a clear role and none feels redundant.

    Completeness4/5

    The set covers initial setup, device state, design guidance, and multiple rendering/display workflows including text, scenes, HTML, images, and overlays. Minor gaps remain around explicitly pushing or clearing composed scenes and broader lifecycle operations, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources