Spiritmarch Aseprite MCP
Provides tools for interacting with Aseprite, including sprite inspection, applying ordered patch operations, exporting/previewing artifacts, and committing project files.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Spiritmarch Aseprite MCP Inspect my character sprite and export a preview to the staging workspace."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
"""Spiritmarch Aseprite MCP — CLI-first fork of diivi/aseprite-mcp.
Six tools with staging workspaces. Project files are only written via
file_commit. Inspired by SpriteRelay's CLI write-boundary model;
not affiliated with SpriteRelay.
Tools
aseprite_doctor— locate Aseprite, version, Lua probesprite_inspect— open into staging, sprite_info, operation catalogsprite_patch— apply ordered ops to staged copy (one batch launch)sprite_export/sprite_preview— artifacts under the workspacefile_commit— promote / rollback / verify / discard
Related MCP server: aseprite-mcp
Run
uv sync
export ASEPRITE_PATH=/Applications/Aseprite.app/Contents/MacOS/aseprite
uv run -m sm_asepriteCursor mcp.json:
"aseprite": {
"command": "/Users/YOU/.local/bin/uv",
"args": ["--directory", "/Users/frederiek/Herd/Personal/spiritmarch-aseprite-mcp", "run", "-m", "sm_aseprite"],
"env": {
"ASEPRITE_PATH": "/Applications/Aseprite.app/Contents/MacOS/aseprite"
}
}Staging root: /tmp/spiritmarch-aseprite/ (override with SPIRITMARCH_ASEPRITE_ROOT).
Upstream: https://github.com/diivi/aseprite-mcp (git remote upstream).
Available Tools
6 toolsaseprite_doctorA
Find Aseprite, validate version/Lua, report capability flags.
Args: mode: "full" (default) or "path" for a quick binary check.
Inputs: mode.
file_commitA
Promote staged artifacts to a project path, or rollback/verify.
Modes: commit_single — copy staged sprite (or artifact) to destination; writes .bak on overwrite rollback_single — restore destination from destination.bak verify_commit — check destination / .bak presence discard_workspace — delete staging workspace directory
Inputs: mode (required), artifact, destination, workspace_id.
sprite_exportC
Export staged artifacts (PNG/GIF/sheet) into the workspace artifacts folder.
Modes: frame | gif | spritesheet
Inputs: workspace_id (required), mode, scale, filename, +1 more.
sprite_inspectA
Read sprites, workspaces, and the operation catalog.
Modes: open — copy path into a new staging workspace; returns workspace_id sprite_info — metadata for staged sprite (needs workspace_id) list_layers — layer tree JSON (needs workspace_id) list_workspaces — ids under the staging root operation_list — public patch operations (optional family filter) operation_describe — schema for one op (name=)
Inputs: mode (required), name, path, family, +1 more.
sprite_patchA
Validate and apply an ordered operation list to the staged sprite copy.
Args: workspace_id: Staging workspace from sprite_inspect mode=open operations_json: JSON array of objects, each with "op" and params
Inputs: workspace_id (required), operations_json (required).
sprite_previewB
Render a scaled still of a staged frame for review (writes under workspace artifacts).
Inputs: workspace_id (required), scale, frame_index.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct stage in the workflow: environment validation, inspection/staging, patching, previewing, exporting, and committing. sprite_preview and sprite_export are separated by review versus final artifact generation, while file_commit covers destination promotion rather than workspace artifact creation.
Most tools follow a clear object_verb snake_case pattern: sprite_inspect, sprite_patch, sprite_export, and file_commit. aseprite_doctor breaks this pattern by using a noun/agentive name, but the remaining names are predictable and readable.
Six tools is well-scoped for an Aseprite staging workflow, with each tool representing a meaningful phase: check, inspect, patch, preview, export, and commit. There is no bloat and no sense that the set is too thin.
The tool surface covers the full lifecycle from environment validation, opening and inspecting sprites, applying patch operations, previewing, exporting, and committing or rolling back changes. The operation catalog and workspace management modes fill gaps that would otherwise require external tooling.
Related MCP Connectors
Build and publish pages, manage collections, records and files in a Markerloop workspace.
Control Unreal Engine to browse assets, import content, and manage levels and sequences. Automate…
Drive a live Cinevva game session: edit game files, import CC0 assets, preview changes.
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI assistants to automate Aseprite tasks such as sprite sheet export, frame extraction, and Lua scripting for sprite manipulation.2135 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables 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