Spiritmarch Aseprite MCP
"""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 probe
- `sprite_inspect` — open into staging, sprite_info, operation catalog
- `sprite_patch` — apply ordered ops to staged copy (one batch launch)
- `sprite_export` / `sprite_preview` — artifacts under the workspace
- `file_commit` — promote / rollback / verify / discard
## Run
```bash
uv sync
export ASEPRITE_PATH=/Applications/Aseprite.app/Contents/MacOS/aseprite
uv run -m sm_aseprite
```
Cursor `mcp.json`:
```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`).
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.