aseprite-mcp
Related Servers
Alternatives to aseprite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP 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
- AlicenseBqualityAmaintenanceAn MCP server that lets AI agents create and edit Aseprite sprites headlessly, enabling pixel art, animation, and export via 98 tools.15618MIT
- 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.38,290 npmMIT
- AlicenseCqualityAmaintenanceMCP server for creating pixel art, characters, and scenes for Aseprite, generating deterministic plans and Godot-compatible manifests.185297 npm1MIT
- AlicenseAqualityBmaintenanceMCP server that forges pixel art sprites & game assets using Google Gemini — generate, crop, split & process, all from your AI assistant.840 npm5MIT
- FlicenseBqualityCmaintenanceMCP server for controlling Aseprite from Codex, wrapping its native CLI and Lua scripting to enable pixel art creation, sprite editing, animation, file inspection, and export.8-
TDQS
Scored across 43 tools
Most tools have clearly distinct targets and actions, but a few boundaries blur: open_sprite and get_sprite_info both return metadata, get_sprite_info aggregates data also available from list_layers/list_frames/get_palette, and draw_circle/draw_ellipse are mathematically similar. Descriptions are clear enough that agents can mostly avoid misselection, but occasional overlap remains.
The tool set consistently uses snake_case verb-first names with predictable prefixes like list_, remove_, set_, and export_. Minor deviations prevent a perfect score: create_sprite/create_tag/create_slice versus add_layer/add_frame, plus bare action names like merge_down and outline.
43 tools is well above the typical well-scoped range and passes the 25+ threshold, creating a heavy action-selection burden for agents. While Aseprite is a broad editor, the count could be reduced by consolidating similar drawing and export operations.
The surface covers the full core sprite-editing lifecycle: sprite create/open/save/transform, layer/frame/cel management, palette and tag operations, drawing primitives, multiple export modes, and run_script as an advanced escape hatch. Workflows have no obvious dead ends for typical Aseprite tasks.