Create pixel art and animations through local Aseprite integrations. For Cursor, 1 route is explicitly documented by the integration maintainer.
A Python MCP server and Lua plugin work with the active sprite in Aseprite.
Platforms: Not documented
MCP support suggests compatibility; this client is not documented by the maintainer.
Aseprite 1.3 or newer, the Aseprite extension and uvx.
Aseprite must be running with the extension enabled to edit the active sprite.
An MCP server supports both live Aseprite sessions and headless file workflows.
Platforms: macOS, Windows, Linux
The integration documentation explicitly names this client.
Aseprite 1.3 and Node.js 20 or newer.
Batch mode starts a fresh headless process per call; unsaved state does not carry between calls.
| Integration | Cursor compatibility | Requirements |
|---|---|---|
| Aseprite MCP · giangdvdotdev | MCP compatibility (inferred) | Aseprite 1.3 or newer, the Aseprite extension and uvx. |
| Aseprite MCP · shin2344234 | Documented setup Setup guide | Aseprite 1.3 and Node.js 20 or newer. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Cursor and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Aseprite integrations