A
licenseNot graded
qualityD
maintenanceMCP server for programmatically creating and editing Aseprite sprites, enabling AI agents to draw, manage layers and frames, and iterate until the desired result is achieved.
MIT
Aseprite Asset MCP
by jdsalasca
Related Servers
Alternatives to Aseprite Asset MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for Aseprite — create, edit, and export pixel art sprites, animations, and sprite sheets from any AI assistant.437MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that lets AI agents draw in a live Aseprite editor or headless mode, featuring one-action Unity sprite-sheet export, art-QA sweeps, and game-dev tools.76 PyPI7MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI agents create, edit, and animate pixel-art sprites, with PNG previews after every step and support for export to GIF/APNG/spritesheets.45,854 npmMIT
- AlicenseBqualityCmaintenanceAn MCP server that lets AI agents create and edit Aseprite sprites headlessly, enabling pixel art, animation, and export via 98 tools.10010MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for safe local automation of Aseprite, providing tools to create, inspect, edit, save, and export pixel art documents through the official Aseprite CLI and controlled Lua scripts.-
TDQS
C2.6/5.0
Scored across 185 tools
Disambiguation2/5
Many tools perform nearly the same operation with small variations, such as draw_pixels/draw_pixels_at, adjust_hsl/adjust_hsl_native, apply_dither_gradient/apply_dither_pattern, and numerous generate_*_pack/compose_*_scene generators. The descriptions help, but the boundaries are not obvious from names alone, so an agent can easily pick the wrong variant.
Naming Consistency4/5
The overwhelming majority of tools use a readable snake_case verb_noun pattern (create_canvas, export_sprite, get_palette, set_frame_duration), and _at suffixes consistently mark layer/frame-targeted variants. Minor exceptions like server_capabilities, animation_workflow_guide, and outline_native break the pattern but do not obscure the overall scheme.
Tool Count1/5
185 tools is far beyond a well-scoped MCP surface; even a comprehensive Aseprite workflow does not need this many first-class entry points. This is an extreme count that will force agents to spend excessive tokens and effort on tool selection.
Completeness4/5
The surface is unusually broad: document/layer/frame/cel editing, palettes, tilemaps, text, slices, animation, exports, batch jobs, and procedural asset generation are all covered. Minor lifecycle gaps such as no explicit document save/close/delete and only validated onion-skin settings remain, but run_lua_script and export tools provide workarounds.
Maintenance
ActivityMaintained
ResponsivenessNo issues