aseprite-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASEPRITE_PATH | No | Path to the Aseprite executable. If not set, the server will search PATH and common macOS locations. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aseprite_list_commandsA | List Aseprite command IDs known from the upstream commands_list.h. |
| aseprite_command_sequenceA | Run Aseprite app.command.(params) actions through Lua, optionally opening files and saving the active sprite. |
| aseprite_statusB | Resolve the Aseprite executable and report version/configuration. |
| aseprite_cliA | Run raw Aseprite CLI arguments. Use for any native capability not covered by a higher-level tool. |
| aseprite_run_luaB | Execute an inline or file-based Aseprite Lua script, optionally opening input sprites first. |
| aseprite_create_spriteC | Create a sprite from structured drawing operations. Supports dryRun to inspect generated Lua. |
| aseprite_exportB | Export an existing Aseprite file/image to PNG/GIF/sheet/data using common CLI flags. |
| aseprite_sprite_infoA | Open a sprite and return metadata about size, frames, layers, and tags. |
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 8 tools
Most tools have clearly distinct purposes: status, listing commands, command sequences, raw CLI, Lua, create, export, info. However, aseprite_cli overlaps with many others since it can perform any of those actions, and aseprite_command_sequence and aseprite_run_lua both execute Lua, creating some ambiguity.
All tools share the aseprite_ prefix and use snake_case, but the pattern is mixed: some are verb_noun (list_commands, run_lua, create_sprite), some are noun-only (status, cli), and others are noun_noun (command_sequence, sprite_info). This inconsistency reduces predictability, though names remain readable.
8 tools is well within the ideal 3-15 range and appropriate for covering Aseprite's main capabilities: status, command introspection, execution, scripting, creation, export, and metadata. Each tool earns its place without bloat.
Core workflows are well covered: create, export, inspect, run commands/scripts, and get config. Minor gaps exist, such as no high-level edit/modify tool, but aseprite_run_lua and aseprite_cli provide escape hatches for any missing operations, making the surface reasonably complete.