Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

Related Servers

Alternatives to pixelorama-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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.
      13
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to directly control Pixelorama for real-time 2D game asset creation, including layer-based pixel drawing, animation frames, automatic quality checks, and export of spritesheets, .pxo files, and Godot resources.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables an AI agent to create and edit pixel art directly in Aseprite — building sprites, layers, frames, animation tags and palettes, painting pixels and primitives, inspecting the rendered result, and exporting GIFs or sprite sheets. All work lands on real .aseprite files that can be opened and edited by hand.
      43
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to create and revise editable pixel art in a running Aseprite editor, with live tools for sprites, layers, drawing, animation, palettes, selections, previews, saving, and exporting.
      MIT
    • 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

    TDQS

    B3.4/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target clearly distinct operations: draw_pixels vs fill_rect vs clear_cel, and add_layer vs add_frame vs select_cel are easy to separate. The closest pair is get_image (blended visual preview) vs read_pixels (raw grid data) and get_project (metadata), but the descriptions make the distinction clear enough.

    Naming Consistency4/5

    Nearly all names follow a snake_case verb_noun or verb_target pattern (get_project, draw_pixels, rename_layer, resize_canvas, export_png), with only bare verbs undo/redo as a natural exception. Minor deviation: the create verb is inconsistent ('new_project' vs 'create_palette', 'add_layer', 'add_frame').

    Tool Count4/5

    21 tools is on the heavy side but each maps to a real pixel-art workflow: project lifecycle, drawing, layers, frames, palettes, and export. Nothing looks redundant, though a few could be consolidated (e.g. layer/frame manipulation helpers).

    Completeness3/5

    Core creation flows are covered (new/open project, draw, fill, layers, frames, palettes, save/export, undo/redo), but the lifecycle is asymmetric: you can add layers and frames yet there is no delete_layer, delete_frame, duplicate_frame, or layer reordering/visibility toggle. These are common operations that will force agents into workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues