Spiritmarch Aseprite MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASEPRITE_PATH | Yes | Path to the Aseprite executable | |
| SPIRITMARCH_ASEPRITE_ROOT | No | Override for the staging root (default: /tmp/spiritmarch-aseprite/) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aseprite_doctorA | Find Aseprite, validate version/Lua, report capability flags. Args: mode: "full" (default) or "path" for a quick binary check. |
| 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=) |
| 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 |
| sprite_exportC | Export staged artifacts (PNG/GIF/sheet) into the workspace artifacts folder. Modes: frame | gif | spritesheet |
| sprite_previewB | Render a scaled still of a staged frame for review (writes under workspace artifacts). |
| 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.