Aseprite MCP Server
Related Servers
Alternatives to Aseprite MCP Server
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.43120 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to create, draw, and refine Aseprite documents through deterministic canvas, layer, frame, tag, and palette tools, with pixel analyzers, style validation, and preview/diff visual feedback. It also supports spritesheet and animated GIF export, producing multi-layer game-ready assets.1MIT
- 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.73120 npmMIT
- 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
- AlicenseAqualityBmaintenanceEnables LLM agents to create pixel art and animations in Aseprite by writing and headlessly executing complete Lua scripts, with API documentation and output verification.2206 npm1MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to draw, animate, and export game-ready pixel art and sprite sheets through a local Aseprite installation, including palette work, layer rigging, and cleanup of AI-generated frames. It also offers a CLI for running the same animation recipes in a game asset pipeline.17120 npmMIT
TDQS
Scored across 12 tools
Most tools have clearly distinct resource+action targets, but aseprite_run_lua and aseprite_run_pipeline both execute workflows and could be confused, and aseprite_analyze_style partially overlaps palette/inspection concerns of aseprite_apply_palette and aseprite_inspect_sprite.
Every tool uses the aseprite_ prefix with a consistent verb_noun pattern (create_sprite, draw_pixels, apply_palette, export_spritesheet, inspect_sprite, run_lua), making the set highly predictable.
12 tools is a well-scoped size for a sprite-editing server, covering distinct phases (info, create, draw, animate, palette, export, inspect) without obvious redundancy.
Core pixel-art lifecycle is covered from creation through drawing, animation, palette, export, and inspection, but there are gaps in editing existing sprites (e.g. add/remove layers or frames, delete/resize operations) that could create dead ends for iterative workflows.