Aseprite Live vs Funplay Cocos MCP
A side-by-side look at the Aseprite Live and Funplay Cocos MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aseprite Live for gaming work as a local process; choose Funplay Cocos MCP 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 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.
Choose Funplay Cocos MCP when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 52/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | ASEPRITE_MCP_BACKENDASEPRITE_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 350 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 80 | Not listed |
| Full listing | View Aseprite Live | View Funplay Cocos MCP |
Tools & capabilities
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
Funplay Cocos MCP tools
No tool names declared yet. Check the project README from 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.
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"
}
}
}
}
Funplay Cocos MCP
{
"mcpServers": {
"funplay-cocos-mcp": {
"command": "npx",
"args": [
"-y",
"funplay-cocos-mcp"
]
}
}
}
Frequently asked questions
Aseprite Live is categorized under Gaming and uses a local stdio subprocess. Funplay Cocos MCP belongs to Gaming and uses a local stdio subprocess. Pick Aseprite Live for gaming work and Funplay Cocos MCP 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.
Aseprite Live has no declared pricing — check the project's own site. Funplay Cocos MCP is listed as free. Auth: no auth required. 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 aseprite-live and funplay-cocos-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aseprite Live has a quality signal of 52/100 (Good) with 3 views, 0 installs and 8 GitHub stars. Funplay Cocos MCP has 52/100 (Good) with 1 views, 0 installs and 350 GitHub stars.