Spiritmarch Aseprite MCP
Related Servers
Alternatives to Spiritmarch Aseprite MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to drive Aseprite for pixel-art creation, including sprite setup, grid-based drawing, layer/frame/tag management, reference image import, and export, with rendered previews after every mutation.MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to automate Aseprite tasks such as sprite sheet export, frame extraction, and Lua scripting for sprite manipulation.2115 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to create and edit pixel art and animated sprites in Aseprite through 104 tools covering drawing, layers, animation, palettes, tilemaps, exports, visual analysis, and raw Lua scripting.116MIT
- FlicenseBqualityCmaintenanceEnables users to automate the creation, editing, animation, and export of pixel-art game assets through a multi-agent pipeline that derives style specs and blueprints, generates Lua build scripts, and drives the canvas editor to produce .aseprite files, spritesheets, atlases, GIFs, and previews.12-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to create, draw, and refine Aseprite documents through deterministic canvas, layer, frame, tag, and palette tools, with pixel analyzers, style validation, and preview/diff visual feedback. It also supports spritesheet and animated GIF export, producing multi-layer game-ready assets.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, inspect, edit, and export pixel art, sprites, animations, and spritesheets using headless Aseprite, and to convert arbitrary images into indexed pixel art.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct stage in the workflow: environment validation, inspection/staging, patching, previewing, exporting, and committing. sprite_preview and sprite_export are separated by review versus final artifact generation, while file_commit covers destination promotion rather than workspace artifact creation.
Most tools follow a clear object_verb snake_case pattern: sprite_inspect, sprite_patch, sprite_export, and file_commit. aseprite_doctor breaks this pattern by using a noun/agentive name, but the remaining names are predictable and readable.
Six tools is well-scoped for an Aseprite staging workflow, with each tool representing a meaningful phase: check, inspect, patch, preview, export, and commit. There is no bloat and no sense that the set is too thin.
The tool surface covers the full lifecycle from environment validation, opening and inspecting sprites, applying patch operations, previewing, exporting, and committing or rolling back changes. The operation catalog and workspace management modes fill gaps that would otherwise require external tooling.