Aseprite MCP Tools MCP Server

MCP server for interacting with the Aseprite API. The aseprite mcp tools mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

A Python MCP server that gives AI assistants full control over Aseprite for creating pixel art and animated sprites.

Its toolset

Everything the assistant can do here goes through one of these:

• Canvas — The Canvas tool exposed by this server
• Drawing — All _at variants target a specific layer/frame and can create the cel on demand. Coordinates are sprite-global
• Text — Aseprite's Lua API has no text drawing, so glyphs are rasterised on the server and composited into the sprite. Two font backends are supported
• Layers — The Layers tool exposed by this server
• Effects — The pixel-art toolbox: clean outlines, palette-respecting blends, and shading variants
• Animation — The Animation tool exposed by this server
• Palette — The Palette tool exposed by this server
• Transform — The Transform tool exposed by this server
• Slices — The Slices tool exposed by this server
• Tilemap — The Tilemap tool exposed by this server
• Inspection — The Inspection tool exposed by this server
• Quality — The Quality tool exposed by this server

Configuration

You will need one environment variable: ASEPRITE_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.13+ - uv package manager - Aseprite (set ASEPRITE_PATH in .env if it is not on your PATH)

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Aseprite MCP Tools's toolset — Canvas, Drawing, Text and 11 more — is a fair guide to whether it matches your workflow. It is maintained by diivi; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Aseprite MCP Tools's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Aseprite MCP Tools.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the aseprite mcp tools mcp server does with a few real requests.