F
licenseNot graded
qualityD
maintenanceMCP 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.
-
aseprite-mcp
by Ryan3719
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
- AlicenseBqualityDmaintenanceMCP server for Aseprite — create, edit, and export pixel art sprites, animations, and sprite sheets from any AI assistant.437MIT
- AlicenseNot gradedqualityCmaintenanceA TypeScript MCP server that exposes Aseprite to LLM clients as 76 tools for drawing, layers, frames, palettes, and more by generating Lua scripts and running Aseprite headlessly.46 npmMIT
- AlicenseAqualityDmaintenanceA Python MCP server enabling programmatic interaction with Aseprite for pixel art creation and manipulation with features like drawing operations, palette management, and batch processing.1924MIT
- AlicenseBqualityAmaintenanceAn MCP server that lets AI agents create and edit Aseprite sprites headlessly, enabling pixel art, animation, and export via 98 tools.15618MIT
TDQS
B3.4/5.0
Scored across 8 tools
Disambiguation4/5
Most tools have clearly distinct purposes: status, listing commands, command sequences, raw CLI, Lua, create, export, info. However, aseprite_cli overlaps with many others since it can perform any of those actions, and aseprite_command_sequence and aseprite_run_lua both execute Lua, creating some ambiguity.
Naming Consistency3/5
All tools share the aseprite_ prefix and use snake_case, but the pattern is mixed: some are verb_noun (list_commands, run_lua, create_sprite), some are noun-only (status, cli), and others are noun_noun (command_sequence, sprite_info). This inconsistency reduces predictability, though names remain readable.
Tool Count5/5
8 tools is well within the ideal 3-15 range and appropriate for covering Aseprite's main capabilities: status, command introspection, execution, scripting, creation, export, and metadata. Each tool earns its place without bloat.
Completeness4/5
Core workflows are well covered: create, export, inspect, run commands/scripts, and get config. Minor gaps exist, such as no high-level edit/modify tool, but aseprite_run_lua and aseprite_cli provide escape hatches for any missing operations, making the surface reasonably complete.
Maintenance
ActivityStale
ResponsivenessSyncing