aseprite-mcp
Related Servers
Alternatives to aseprite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI assistants to create and edit pixel art and sprite animations by driving Aseprite's 73 tools for sprites, layers, frames, cels, drawing, selections, palettes, tags, slices, tilemaps, filters and export, with a generic escape hatch to any of its 183 menu commands or Lua scripting API. It runs either headless in batch mode on files or live against an open Aseprite window so edits are visible and undoable.73115 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to drive Aseprite for pixel-art creation, including sprite setup, grid-based drawing, layer/frame/tag management, reference image import, and export, with rendered previews after every mutation.MIT
- 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.43115 npm1MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to automate Aseprite tasks such as sprite sheet export, frame extraction, and Lua scripting for sprite manipulation.2126 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI sprite generation and semantic tools for Aseprite, allowing LLMs to create pixel art, add animations, and manage projects with visual feedback.61GPL 3.0
- AlicenseBqualityCmaintenanceEnables AI assistants to create and edit pixel art and animated sprites in Aseprite through 104 tools covering drawing, layers, animation, palettes, tilemaps, exports, visual analysis, and raw Lua scripting.116MIT
TDQS
Scored across 17 tools
Most tools target clearly distinct operations (draw vs edit vs animate vs generate vs character), with detailed descriptions that help separate them. Minor overlap exists between create_sprite's image import and ingest's frame import, and palette colors can also be read via sprite_info, but these are edge confusions rather than core ambiguity.
Mixed conventions: some tools use verb_noun (create_sprite, read_pixels, run_lua), many are bare verbs (draw, edit, resize, export, animate), and others are nouns (palette, layer, frames, character, batch). It's readable and each name hints at its domain, but there's no single predictable pattern.
17 tools is slightly above the ideal 3-15 range, but each tool bundles a coherent family of operations (edit, animate, character) rather than being a redundant one-off. The breadth of the pixel-art workflow (create, edit, animate, AI-generate, export) justifies the count.
The surface covers creation, editing, animation, AI ingestion/generation, and export with good lifecycle depth. Some gaps remain (no dedicated text, selection/tilemap, or undo/redo tooling), but run_lua serves as an escape hatch for arbitrary Aseprite Lua operations.