Immediate visual control
Work in the document already open in Aseprite. Existing-document patches form one labelled native undo step; new-document creation is the exception.
Local Aseprite MCP // Live + Staged
Edit live. Stage safely. Stay in control.
Connect a compatible AI assistant or agent to editable .aseprite projects through local Model Context Protocol software. Edit the open document with Live, or inspect, preview, commit, and verify through CLI's staged production workflow.
Control at every step
Inspect layers, frames, tags, linked cels, palettes, and available capabilities.
Use structured operations in the open document or a staged working copy.
Render previews, compare changes, and inspect animation behavior before accepting it.
Undo an existing-document Live patch, or explicitly commit and roll back staged work.
Work in the document already open in Aseprite. Existing-document patches form one labelled native undo step; new-document creation is the exception.
Work in a retained staged copy, then explicitly commit. Overwrites create backups; manifest commits add durable journals, verification, and rollback.
Buyer confidence
.aseprite layers, frames, tags, palettes, and linked cels.One-time pricing
$14.99 once
Use Live for immediate iteration and CLI for controlled release work.
$7.99 once
Work in a retained staged copy so project files change only when you explicitly commit.
$11.99 once
Inspect and change the document already open in Aseprite, see the result immediately, then continue or undo.
One-time USD prices, licensed per natural person. Aseprite is required and licensed separately.
| Question | SpriteRelay CLI | SpriteRelay Live |
|---|---|---|
| Must Aseprite be open? | No. It launches licensed Aseprite in batch mode. | Yes. It works with the running editor and active document. |
| Where do edits happen? | In a retained temporary working copy. | Immediately in the attached document. |
| How do I recover? | Discard staged work before commit. Overwrites create backups; manifest commits add durable journals, verification, and rollback. | One labeled native undo step for an existing-document patch. Creating a new document is outside existing undo history. |
| Best for | Repeatable batch production, exports, and controlled release work. | Visual iteration in the document already open in Aseprite. |
Included with your purchase
You receive the files for the product you choose. Complete includes both private packages and the matched Live Bridge.
.tgz files, according to your purchase.AI-assisted pixel art animation in the open Aseprite document.
Watch Live demo on YouTubeAI-assisted pixel art automation through a staged Aseprite workflow.
Watch CLI demo on YouTubeWhy SpriteRelay
Use Live for immediate visual decisions and CLI for controlled production changes without giving up source structure or a clear recovery path.
Use an AI assistant to inspect and change the active document while Aseprite remains open, see the result immediately, then continue or undo without leaving the editor.
Existing-document patches form one labelled native undo step. Creating a new document is the exception.
Watch the Live demoRun batch sprite workflows in a retained temporary working copy: inspect, patch, preview, and export before choosing what is written to a production path.
file_commit is the only caller-path writer. It supports backups when overwriting, durable manifest journals, journal-based post-commit verification, and rollback.
Read document structure, render previews, compare changes, and inspect animation behavior before accepting or delivering work.
Use immediate visual feedback in Live or review staged artifacts in CLI.
Technical interface
SpriteRelay groups a wide Aseprite operation set into a small number of purpose-built tools, helping agents choose the right action without navigating hundreds of endpoints or exposing an arbitrary-code channel.
Six purpose-built tools group typed operation families behind clear boundaries, giving the agent fewer top-level routes to evaluate.
Designed to reduce tool-schema context and repeated definition tokens while making operation selection clearer. Actual token use depends on the MCP client, model, and request.Frequently asked questions
SpriteRelay is local Aseprite MCP software. Live edits the active document through the matched Bridge; CLI stages batch automation before an explicit production commit.
It is a Model Context Protocol workflow that gives a compatible AI assistant structured tools for Aseprite. Read the Aseprite MCP guide.
Live targets the document open in Aseprite for immediate iteration. CLI works in a staged copy for batch and controlled production work, with preview and explicit commit. Overwrites create backups, while manifest commits support durable journals, verification, and rollback.
You need Node.js 18 or newer, your own licensed Aseprite installation, and an MCP client that supports local stdio servers. Live also requires Aseprite to remain open with the matched Bridge installed.
Yes. One licensed person may use SpriteRelay on multiple devices they control. Each additional direct user needs a licence unless separate written team or site terms apply. The EULA controls.
A licence includes updates within the same major version if released. A future major version may require another purchase, and no future update is promised. See the update terms.
Direct buyers may request a refund within 14 days. For immediately delivered digital content, that right may end after delivery begins if the buyer consented and acknowledged the loss of the right. Storefront terms and mandatory law also apply; see the refund terms.
Best-effort installation, compatibility, documentation, and reproducible-bug support may be available at support@spriterelay.com. Response and resolution times are not guaranteed.
The current CLI baseline is Aseprite 1.3.18.1 with Lua API 40. Live requires Aseprite 1.3-rc5 or newer with Lua API 25 or newer. Version-sensitive CLI features are capability-gated.
Complete contains SpriteRelay Live, SpriteRelay CLI, and the matched SpriteRelay Live Bridge under one per-user licence.
An interrupted mutation is marked uncertain and is never silently replayed. Inspect the document and undo if needed before continuing.
CLI changes staged copies until file_commit. Live patches the open document but does not save it to disk; existing-document patches form one undo step, with new-document creation as the exception. Permanent exports require an explicit commit; manifest commits use durable journals.
SpriteRelay itself does not upload artwork during ordinary use; core processing and optional diagnostics stay on your device. Your MCP client or AI provider may process data under its own privacy terms. Read how SpriteRelay handles local processing or the privacy terms.
No. Both products accept validated operations; neither exposes a raw-Lua or arbitrary-code channel.
Live when creating. Staged when shipping.
One-time, per-user purchase. Aseprite licensed separately. EULA terms apply.