Aseprite AI Artist
Related Servers
Alternatives to Aseprite AI Artist
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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.4395 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to create and edit pixel art in a live Aseprite window, with tools for drawing, selection, transformation, and animation.18819 npm571MIT
- AlicenseAqualityBmaintenanceEnables AI to create pixel art in Aseprite through pixel-level drawing primitives, read canvas screenshots, and iterate until satisfied.317MIT
- AlicenseBqualityBmaintenanceEnables AI agents to create and refine pixel art and sprite animations through MCP tools, including seeded generators, indexed palettes, shading, animation presets, inline PNG previews, and multi-format export.28MIT
- 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.95 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to draw pixel art live in Aseprite by running one JavaScript program per step, with each program committing as a single undo step. It exposes a single execute tool for creating sprites, drawing, animating, and exporting sheets and GIFs.95 npm-
TDQS
Scored across 18 tools
Most tools target clearly distinct domains (frames, layers, cels, tags, palette, tileset, export), and several descriptions explicitly draw boundaries, e.g. 'look' vs 'read_pixels' and 'draw' vs 'transform'. A few residual overlaps remain: draw's 'replace' op vs recolor's 'replace', cel op 'set' position vs transform 'translate', cel 'copy' vs layer 'duplicate', and select 'color' vs recolor ops — an agent could reasonably pick either in those cases.
All names are lowercase snake_case with no camelCase mixing, and the multi-op consolidation ('op' parameter) is applied uniformly. The only deviation is stylistic: some tools are bare nouns (layer, frame, cel, palette) while others are verbs (draw, export, validate, recolor), plus a couple of noun_verb names (sprite_info, sprite_manage, read_pixels).
18 tools sits at the upper end but is justified by the breadth of the domain (sprite lifecycle, cels, layers, frames, tags, palettes, tilesets, export, validation). The design wisely collapses dozens of operations into op-parameterized tools rather than exploding into 60+ endpoints, so each tool earns its place.
Coverage is unusually thorough: read state, draw, transform, select, recolor, palette management, layer/frame/cel/tag lifecycle, tilesets, validation, reference import and multiple export formats. The main gap is the absence of an explicit undo/redo tool — batching mitigates it, but an agent that corrupts a batch has no direct recovery op, and there is also no scripting/plugin escape hatch.