What is aseprite-mcp?
aseprite-mcp, by the GitHub user giangdvdotdev, pairs a Python MCP server, run with uvx aseprite-mcp, with a Lua extension that loads inside Aseprite 1.3 or newer. The two talk over a WebSocket on 127.0.0.1:9876, so the agent works on the sprite open in your editor rather than on files in the background.
It registers 30 tools that act on the active sprite: creating sprites and layers; drawing pixels in batches, lines, rectangles, ellipses, flood fills and erasing; reading back the canvas image, pixels, regions, layers and selection; undo and redo; adding, timing and deleting frames; opening and saving files; and PNG and spritesheet export. The repository is MIT-licensed with about 13 stars and 5 commits, and version 0.6.0 is on PyPI.
How to install aseprite-mcp
uvx aseprite-mcpIs aseprite-mcp worth it?
aseprite-mcp gets one thing right that many art servers skip: the agent can look at what it drew. get_canvas_image and the pixel and region reads let a model check its sprite between strokes, the editor shows each change as it lands, and undo and redo are tools, so a bad pass can be stepped back without a person reaching for the keyboard.
The output is bounded by the model, not the server. The README gallery shows a dog walk cycle and a portrait drawn from a photo by Claude Code on Opus 5, and a rubber duck from a local Gemma 4 26B model on a 12 GB RTX 3060, a useful sign that small local models can drive it. Drawing through tool calls is slow and token-hungry for anything past small sprites, and the 30 tools include nothing for palettes or tilemaps.
The README states the security position plainly. The WebSocket listener has no authentication; it binds 127.0.0.1, so other machines cannot reach it, but any process on the same computer can drive Aseprite while the server runs. export_png, save_sprite and export_spritesheet write to any absolute path they are given and overwrite what is there, so a confused agent can clobber files outside the project.
It is a one-person project with 5 commits in its public history and two test suites, pytest for the server and a Lua runner for the plugin, that run without Aseprite open. ASEPRITE_MCP_PORT has to match on both ends because nothing negotiates the port. The default 9876 sits next to the 9877 used by both Ableton servers, and the README's own example of moving it picks 9877, which would collide with either of them.
Where it earns its place
A solo developer making a 2D platformer
Block out a 32×32 enemy sprite and a short walk cycle
Ask for the sprite, then extra frames with set durations, and export a spritesheet straight into the game's asset folder. Free apart from the model; expect to repaint details by hand.
A three-person game-jam team
Get placeholder art on screen while the others write code
One person directs the agent in Aseprite; its sketches are good enough to test gameplay and get replaced later. Running a local model, as the gallery's RTX 3060 example does, keeps API cost at zero.
A pixel-art tutor
Show students how a shape is built up pixel by pixel
Students watch the agent draw on the shared screen, then use undo to step back through the strokes and redraw them by hand. The only cost is the model it runs on.
Before you commit
- Setup
- Add uvx aseprite-mcp to the client, install the .aseprite-extension file from the latest release, restart Aseprite and look for [MCP] Connected. in View > Console. Either end can start first; the plugin retries until the server appears.
- Integrations
- Claude Code, Claude Desktop and other stdio clients; local models through agents such as Pi Agent, per the gallery. Needs Aseprite 1.3 or newer.
- Data and privacy
- Everything runs locally; canvas images and pixels the agent reads back go to your model provider. The WebSocket on 127.0.0.1:9876 has no authentication.
- Limits
- 30 tools, all on the active sprite; no palette or tilemap tools; ASEPRITE_MCP_PORT must match on both ends; save and export tools overwrite files at any absolute path.
What’s good
- Draws live in the real editor, visible as it happens
- Canvas read-back lets the model check its work
- Frames and spritesheet export for simple animation
- Works with small local models, per the gallery
What’s not
- Unauthenticated local WebSocket
- Export tools overwrite any absolute path
- Two pieces to install, kept on one port by hand
- One maintainer and about 13 stars
Best for
Indie game developers and hobbyists on Aseprite who want an agent to rough out small sprites and simple animation cycles that they then clean up by hand.
aseprite-mcp alternatives
aseprite-mcp: common questions
- Is aseprite-mcp worth it?
- A tidy little bridge that lets an agent rough out sprites in the real editor and see its own work, too young and too narrow to be more than a sketching aid. We rate it 3.4 out of 5.
- How much does aseprite-mcp cost?
- Free and open source (MIT). Requires your own copy of Aseprite 1.3 or newer.
- What are the downsides of aseprite-mcp?
- Unauthenticated local WebSocket; export tools overwrite any absolute path; two pieces to install, kept on one port by hand; one maintainer and about 13 stars.
- Who is aseprite-mcp best for?
- Indie game developers and hobbyists on Aseprite who want an agent to rough out small sprites and simple animation cycles that they then clean up by hand.
- Is aseprite-mcp safe for company data?
- Everything runs locally; canvas images and pixels the agent reads back go to your model provider. The WebSocket on 127.0.0.1:9876 has no authentication.
- What are the best aseprite-mcp alternatives?
- The closest alternatives we have reviewed are Photoshop MCP and Godot MCP.
Answers checked Nov 14, 2026.