libresprite-mcp
Related Servers
Alternatives to libresprite-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to visually interact with LibreSprite for real-time pixel art creation and automated drawing with self-healing capabilities.MIT
- AlicenseAqualityBmaintenanceEnables AI to create pixel art in Aseprite through pixel-level drawing primitives, read canvas screenshots, and iterate until satisfied.313MIT
- 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
- 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
- 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
TDQS
Scored across 7 tools
Most tools target distinct actions: create, resize, export, pixel read/write. The main overlap risk is between export_png and get_png_data, since both produce PNG output, though one writes a file and the other returns base64 data.
All tool names follow a consistent snake_case verb_noun pattern: create_sprite, resize_canvas, export_png, get_png_data, get_pixel, set_pixel, set_pixels_bulk. Verbs are clear and predictable.
Seven tools is well-scoped for a sprite manipulation server. Each tool covers a core operation without excessive overlap or unnecessary additions.
The set covers creation, resizing, export, and pixel access, but lacks fundamental sprite editor operations: loading existing sprites, saving/in-place writes, layer/frame enumeration, and canvas metadata. Agents cannot meaningfully inspect or manipulate a sprite's structure beyond individual pixels.