No user-submitted related servers found.
Scored across 23 tools
Each tool targets a distinct task: pixel_map/set_pixels/draw are clearly separated by bulk vs. individual vs. shape drawing, status/sprites by active vs. all sprites, and view/read_pixels by rendered image vs. pixel data. The descriptions explicitly note when to prefer one tool over another, so an agent is unlikely to select the wrong one.
All tools share the aseprite_ prefix and lowercase snake_case, which is predictable and consistent. However, the suffix style mixes verb commands like draw, clear, copy, and view with noun commands like layer, frame, history, palette, and changes, rather than following a strict verb_noun pattern throughout.
At 23 tools, the server sits in the 16-25 range that feels heavy for a single MCP server. That said, Aseprite is a broad pixel-art editor domain and nearly every tool has a distinct purpose, so the count is defensible though not tightly scoped.
Core pixel-art workflows are well covered: file open/new/save, drawing and reading pixels, layer and frame management, animation, palettes, undo/redo, and even collaborative change monitoring. Obvious gaps like canvas resize, layer reordering/opacity, or frame reordering are missing but can generally be worked around with copy and new operations.