Aseprite MCP
Related Servers
Alternatives to Aseprite MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables AI assistants to create and edit pixel art and sprite animations by driving Aseprite's 73 tools for sprites, layers, frames, cels, drawing, selections, palettes, tags, slices, tilemaps, filters and export, with a generic escape hatch to any of its 183 menu commands or Lua scripting API. It runs either headless in batch mode on files or live against an open Aseprite window so edits are visible and undoable.730MIT
- AlicenseNot gradedqualityCmaintenanceGives AI assistants headless control of the pixel-art editor by wrapping its command line and complete Lua scripting API. It enables inspecting sprite metadata, creating new sprites, exporting frames and packed spritesheets, and editing pixels, layers, frames, tags and palettes.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to create and revise editable pixel art in a running Aseprite editor, with live tools for sprites, layers, drawing, animation, palettes, selections, previews, saving, and exporting.0MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to automate Aseprite tasks such as sprite sheet export, frame extraction, and Lua scripting for sprite manipulation.2135 npm1MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to control Aseprite for drawing and editing images through its API.59826MIT
- 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
TDQS
Scored across 9 tools
Each tool targets a clearly distinct editor action: connection status, document listing/info, sprite creation, batched operations, preview, undo/redo, and saving. apply_operations is broad but is explicitly scoped to atomic batches at a revision, so it does not blur with create_sprite, save_sprite, undo, or redo.
All names use snake_case and a predictable verb_noun pattern such as get_connection_status, list_documents, create_sprite, and save_sprite. undo and redo are standardized single-verb actions that remain fully readable and consistent with the lifecycle model.
Nine tools are well scoped for controlling an Aseprite editor session without feeling bloated. Each tool covers a necessary lifecycle area: status, discovery, creation, mutation, preview, history, and persistence.
The surface covers the core create/read/update/preview/save/undo/redo lifecycle and likely exposes most editing via apply_operations. Minor gaps remain, such as explicit document close/delete or export-oriented operations beyond save_sprite, but agents can work around them.