MCP Rack
GitHub

Servers / Aseprite Agent MCP

Aseprite Agent MCP

Pixel-art authoring with atomic previews, strict asset checks and verified Phaser exports. 0.3.0 alpha.

Pythonlocal stdioalphaIn the official registry

Install in Claude Code

claude mcp add aseprite -- uvx aseprite-agent-mcp

For other stdio clients, use the process and arguments after --. Follow the source documentation for runtimes, credentials and application setup.

Owner-built project. Status is maintainer-reported; inclusion is not an independent audit. Version information may lag upstream releases. Listing standards · Read as Markdown

Built on aseprite-mcp by Brendan Malloy (MIT), this local MCP server lets an agent create and edit real Aseprite files and see a rendered preview of its work. It adds atomic editing, strict typed asset contracts, verified Phaser export that compares exported pixels with the reopened master, tool profiles, cast tools, workspace locking and crash-safe saves. It complements GIMP for sprite and animation work.

Review and maturity

Metadata review ·

Release metadata checked at 0.3.0: PyPI package, official MCP Registry entry and tagged source agree. This review did not repeat a clean-machine install or an artist review of the output.

What the status labels mean

Availability

Published as 0.3.0 alpha on PyPI and the official MCP Registry. Local stdio only; there is no hosted endpoint.

What it does

  • Native documents, drawing, layers, cels, palettes, frames, tags and slices
  • Typed batch edits with preview feedback and contract checks for geometry, tags, palette and alpha
  • Phaser sheets, atlas metadata and frame timing checked against reopened native masters
  • Import generated images and assemble animations with shared palettes, anchors and verified sheet bundles

Current limitations

  • Requires a separately installed Aseprite runtime with Lua support. No editor binary is included.
  • Synthetic pipeline checks do not establish artistic quality. An artist-reviewed directional cycle and real game asset proof are tracked separately.
  • Broader inherited-tool resource limits and dedicated resampling and fringe checks need further work.
  • The optional live-editor bridge is not implemented.