SpriteCook vs Aseprite Live
A side-by-side look at the SpriteCook and Aseprite Live MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SpriteCook for gaming work as a local process; choose Aseprite Live for gaming as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SpriteCook when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
Choose Aseprite Live when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ASEPRITE_MCP_BACKEND, ASEPRITE_PATH. - You want tools like
status, get_sprite_info, get_pixel.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 40/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ASEPRITE_MCP_BACKENDASEPRITE_PATH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 8 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 80 |
| Full listing | View SpriteCook | View Aseprite Live |
Tools & capabilities
SpriteCook tools
No tool names declared yet. Check the project README from the listing page.
Aseprite Live tools 80
statusget_sprite_infoget_pixelset_sprite_metadataget_sprite_metadataget_pixelsopen_spritesave_spritepathclose_spriteset_active_spritelist_sprites- +68 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SpriteCook
{
"mcpServers": {
"spritecook": {
"command": "npx",
"args": [
"-y",
"spritecook-mcp"
]
}
}
}
Aseprite Live
{
"mcpServers": {
"aseprite-live": {
"command": "uvx",
"args": [
"aseprite-live-mcp"
],
"env": {
"ASEPRITE_MCP_BACKEND": "YOUR_ASEPRITE_MCP_BACKEND_HERE",
"ASEPRITE_PATH": "YOUR_ASEPRITE_PATH_HERE"
}
}
}
}
Frequently asked questions
SpriteCook is categorized under Gaming and uses a local stdio subprocess. Aseprite Live belongs to Gaming and uses a local stdio subprocess. Pick SpriteCook for gaming work and Aseprite Live for gaming.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SpriteCook has no declared pricing — check the project's own site. Aseprite Live has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add spritecook and aseprite-live as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SpriteCook has a quality signal of 40/100 (Fair) with 3 views, 0 installs and 6 GitHub stars. Aseprite Live has 52/100 (Good) with 3 views, 0 installs and 8 GitHub stars.