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.
120 npm
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.43120 npm7MIT
- AlicenseNot gradedqualityCmaintenanceAn 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.94 PyPI8MIT
- 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.47,127 npmMIT
- AlicenseBqualityAmaintenanceAn MCP server that lets AI agents create and edit Aseprite sprites headlessly, enabling pixel art, animation, and export via 98 tools.15623MIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.120 npmMIT
TDQS
C2.7/5.0
Scored across 185 tools
Disambiguation2/5
Many tools overlap heavily across generation, recipe, export, and drawing families, e.g. create_asset_recipe vs run_asset_recipe vs execute_asset_recipe, generate_asset_preset vs compose_asset_preset, and draw_* vs draw_*_at variants. Descriptions help somewhat, but with 185 tools an agent will struggle to reliably pick the right tool without ambiguity.
Naming Consistency4/5
Most names follow a predictable snake_case verb_noun pattern, such as create_canvas, add_layer, export_spritesheet, and inspect_asset_batch. Minor deviations like get_tools_list instead of list_* and a few noun-first or guide-style names slightly reduce consistency.
Tool Count1/5
185 tools is an extreme mismatch for a single MCP server and far exceeds a well-scoped surface. Many operations could be consolidated or exposed through a smaller, more coherent API.
Completeness5/5
The tool surface covers an unusually broad lifecycle: canvas/layer/frame/cel manipulation, palettes, drawing primitives, text, tilemaps, slices, tags, export/import, asset library, recipes, batch jobs, and preview servers. No obvious domain gaps stand out for the stated Aseprite asset creation purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues