MCP server for interacting with the Aseprite API
MCP server for interacting with the Aseprite API
A Python MCP server that gives AI assistants full control over Aseprite for creating pixel art and animated sprites.
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.
uv package manager - Aseprite (set ASEPRITE_PATH in .env if it is not on your PATH)This listing has no verified copy-paste launch configuration. Use the project documentation to confirm the entry point, runtime and authentication before registering it in your MCP client. A package name or repository alone is not a runnable configuration.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
uv package manager - Aseprite (set ASEPRITE_PATH in .env if it is not on your PATH)| Variable | Description | Required |
|---|---|---|
| ASEPRITE_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.