APPLICATION × AGENT Codex Aseprite integration Create pixel art and animations through local Aseprite integrations. For Codex, 1 route is explicitly documented by the integration maintainer.
MCP · Live app
A Python MCP server and Lua plugin work with the active sprite in Aseprite.
Platforms: Not documented
Codex · MCP compatible MCP support suggests compatibility; this client is not documented by the maintainer.
Requirements and limitations Aseprite 1.3 or newer, the Aseprite extension and uvx.
Aseprite must be running with the extension enabled to edit the active sprite.
MCP · Live & file workflows
An MCP server supports both live Aseprite sessions and headless file workflows.
Platforms: macOS, Windows, Linux
Codex · MCP compatible MCP support suggests compatibility; this client is not documented by the maintainer.
Requirements and limitations 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.
MCP · Headless workflow
A headless Aseprite MCP server for creating and editing sprites and animations.
Platforms: Not documented
Codex · Documented The maintainer documentation explicitly identifies this client.
Requirements and limitations Aseprite 1.3 or newer, Python 3.10 or newer, and the MCP server.
Operations run in separate headless Aseprite processes; the optional GUI companion is for viewing edits.
MCP · Headless workflow
A community MCP server for creating and editing Aseprite sprites and animations.
Platforms: Not documented
Codex · MCP compatible MCP support suggests compatibility; this client is not explicitly documented.
Requirements and limitations Aseprite 1.2.10 or newer with Lua scripting, Node.js 18 or newer, and pnpm.
The HTTP server binds to localhost by default and has no built-in authentication; network exposure requires an authenticated proxy.
Compare the actual routes Can Codex control all of Aseprite? The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Which setup should I use? Choose a route that explicitly documents Codex 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