A
licenseA
qualityD
maintenanceA Python MCP server enabling programmatic interaction with Aseprite for pixel art creation and manipulation with features like drawing operations, palette management, and batch processing.
19
24
MIT
Aseprite MCP Tools
by NosytLabs
Related Servers
Alternatives to Aseprite MCP Tools
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
- AlicenseBqualityCmaintenanceAn MCP server that lets AI agents create and edit Aseprite sprites headlessly, enabling pixel art, animation, and export via 98 tools.10010MIT
- AlicenseBqualityDmaintenanceMCP server for Aseprite — create, edit, and export pixel art sprites, animations, and sprite sheets from any AI assistant.437MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to control Aseprite for creating pixel art and animated sprites, with 104 tools covering canvas, drawing, animation, palettes, effects, and more.100MIT
- 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
C2.8/5.0
Scored across 113 tools
Disambiguation2/5
There are many near-duplicate tools: draw_pixels vs draw_pixels_at, draw_line vs draw_line_at, adjust_hsl vs adjust_hsl_native, outline_cel vs outline_native, and several similar tween functions. While the descriptions often clarify the differences, the sheer overlap makes it easy for an agent to pick the wrong tool.
Naming Consistency3/5
Most tools follow a snake_case verb_noun pattern (draw_line, delete_layer, export_frame), but the pattern breaks down with inconsistent suffixes like draw_pixels vs draw_pixels_at and one-off names like ensure_layers_present, animation_sanitize, and render_onion_skin. The naming is readable but not predictable enough to help an agent infer behavior.
Tool Count1/5
113 tools is far beyond what an agent can reliably navigate, even for a feature-rich domain like pixel art. This is an extreme mismatch between tool count and coherent scope; the server tries to expose every possible operation instead of a focused, curated set.
Completeness4/5
The domain is well covered: drawing, layers, frames, cels, tags, slices, palettes, export, animation helpers, analysis, and a Lua escape hatch for anything missing. Minor gaps exist (no explicit save operation, no frame reordering), but agents can generally complete workflows without dead ends.
Maintenance
ActivityMaintained
ResponsivenessSyncing