Pixelorama MCP
Related Servers
Alternatives to Pixelorama MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to draw and edit pixel art inside the Pixelorama editor through a character-grid and palette format, reading pixels back, managing layers and frames, and saving or exporting projects.21MIT
- 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.-
- 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
- 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
- AlicenseCqualityBmaintenanceEnables AI assistants to control Aseprite for drawing and editing images through its API.591,009MIT
TDQS
Scored across 13 tools
Each tool maps to a distinct action (draw, read, fill, clear, export, select), and descriptions clarify boundaries well. The only mild overlap is get_project (metadata description) versus get_image (rendered preview), but their descriptions make the distinction clear.
All 13 tools use a consistent snake_case verb_noun pattern (get_project, add_layer, draw_pixels, export_png, save_project). No mixing of conventions or vague single-word names.
13 tools sits squarely in the ideal 3-15 range and each one covers a distinct editing or project operation. Nothing feels padded or missing from a count perspective.
Project lifecycle (new/open/save/export) and drawing/reading are well covered, but the surface is create-only for structure: add_layer and add_frame exist with no delete_layer or remove_frame, and there is no layer/frame reordering, visibility, or undo control. Agents will hit dead ends when they need to remove or reorder content.