Aseprite MCP Server
Related Servers
Alternatives to Aseprite MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables an AI agent to create and edit pixel art directly in Aseprite — building sprites, layers, frames, animation tags and palettes, painting pixels and primitives, inspecting the rendered result, and exporting GIFs or sprite sheets. All work lands on real .aseprite files that can be opened and edited by hand.431MIT
- 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
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI to generate and compile Aseprite game art, producing sprite files, sheets, and engine JSON with tools for initialization, briefs, pixel painting, building, validation, and opening in Aseprite.MIT
- 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
- 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 12 tools
Most tools have clearly distinct resource+action targets, but aseprite_run_lua and aseprite_run_pipeline both execute workflows and could be confused, and aseprite_analyze_style partially overlaps palette/inspection concerns of aseprite_apply_palette and aseprite_inspect_sprite.
Every tool uses the aseprite_ prefix with a consistent verb_noun pattern (create_sprite, draw_pixels, apply_palette, export_spritesheet, inspect_sprite, run_lua), making the set highly predictable.
12 tools is a well-scoped size for a sprite-editing server, covering distinct phases (info, create, draw, animate, palette, export, inspect) without obvious redundancy.
Core pixel-art lifecycle is covered from creation through drawing, animation, palette, export, and inspection, but there are gaps in editing existing sprites (e.g. add/remove layers or frames, delete/resize operations) that could create dead ends for iterative workflows.