pixelorama-mcp
Related Servers
Alternatives to pixelorama-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.13MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseBqualityCmaintenanceEnables 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.431MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityDmaintenanceEnables AI assistants to create and manipulate pixel art by providing tools for drawing, layer management, and animation frame control. It supports exporting projects to PNG, GIF, and sprite sheet formats via the Model Context Protocol.2219Apache 2.0
- AlicenseBqualityDmaintenanceEnables LLMs to create and edit pixel art reliably with support for layers, frames, symmetry, and various drawing tools.70MIT No Attribution
TDQS
Scored across 21 tools
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.
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').
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).
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.