A
licenseNot graded
qualityF
maintenanceMCP server for generating style-consistent pixel art assets from PixelLab API, with project management, asset review, and an embedded Claude assistant.
MIT
PixelLab Forge MCP
by rabbitcannon
Related Servers
Alternatives to PixelLab Forge MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for Aseprite — create, edit, and export pixel art sprites, animations, and sprite sheets from any AI assistant.437MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI agents create, edit, and animate pixel-art sprites, with PNG previews after every step and support for export to GIF/APNG/spritesheets.45,854 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Antigravity AI with LibreSprite, enabling real-time pixel art drawing, animation, and manipulation through natural language commands.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for programmatically creating and editing Aseprite sprites, enabling AI agents to draw, manage layers and frames, and iterate until the desired result is achieved.MIT
- AlicenseAqualityBmaintenanceMCP server that forges pixel art sprites & game assets using Google Gemini — generate, crop, split & process, all from your AI assistant.835 npm5MIT
TDQS
B3.1/5.0
Scored across 103 tools
Disambiguation2/5
Many tools have near-overlapping purposes: generate_image, create_image_bitforge, create_image_pixflux, create_image_pixen, and create_image_pro_flash all generate pixel art, and character/animation creation is similarly fragmented across 4dir/8dir/v3/pro/pro_flash and v2/v3 text animation variants. The descriptions try to steer selection, but the boundaries are still unclear enough that an agent will frequently face ambiguous choices.
Naming Consistency3/5
Most names follow a readable verb_noun snake_case pattern, but consistency breaks down with irregular version/engine suffixes like v2, v3, pro, pro_flash, bitforge, pixflux, and pixen pasted onto similar operations. The broader pattern is recognizable, but tool-to-tool naming is not predictable enough to guess the right variant.
Tool Count1/5
103 tools is an extreme count for a single MCP server, driven largely by multiple overlapping engine generations and legacy alternatives for the same core capabilities. This is well beyond a manageable scope and will impose a heavy navigation burden on agents.
Completeness4/5
Domain coverage is very strong: characters, objects, tilesets, UI assets, animations, images, jobs, and talking portraits all have solid create/read/update/delete and conversion workflows. Minor gaps exist—fonts have generate/get but no list/delete, and map objects lack full lifecycle management—but no critical dead ends block the main pixel-art generation workflow.
Maintenance
ActivityMaintained
ResponsivenessNo issues