GameForge MCP
Related Servers
Alternatives to GameForge MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables users to automate the creation, editing, animation, and export of pixel-art game assets through a multi-agent pipeline that derives style specs and blueprints, generates Lua build scripts, and drives the canvas editor to produce .aseprite files, spritesheets, atlases, GIFs, and previews.1272 npm3MIT
- AlicenseBqualityCmaintenanceEnables AI agents to procedurally design and render stylized 2:1 dimetric isometric game assets in Blender, including NPR cel-shaded scenes, modular tilesets, 8-angle avatar turnarounds, and mathematically exact subpixel collision diamonds, with turnkey engine manifests for Phaser, Godot 4, and retro web games.10Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables automated game development by orchestrating multi-agent teams (design, programming, 2D/3D art, supervision, QA) through LangGraph and an MCP gateway that drives Blender, Krita, Godot, and Git to produce runnable game builds.2-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and edit pixel-art projects — sprites, props, palettes, eight-direction animation, and tile-based environments — through a stdio MCP server with discovery, help, and call tools. Agents can build from silhouette to detail, inspect native-scale renders, silhouettes, value maps, and GIF playback, then save every change as versionable source.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI agents draw in a live Aseprite editor or headless mode, featuring one-action Unity sprite-sheet export, art-QA sweeps, and game-dev tools.97 PyPI8MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM and agent hosts to create and manipulate structured game-art documents through typed deterministic MCP operations, render them to SVG/PNG, validate output, inspect visuals, and make targeted edits toward reproducible, game-ready assets.Apache 2.0
TDQS
Scored across 24 tools
Most tools have distinct, well-scoped purposes (engine exports, Blender rigging, atlas compilation), but several overlap in the 'produce character frames/normals' space: synthesize_procedural_frames, blender_ortho_turntable_bake, and compile_sprite_atlas all output sprite frames + normal maps from different sources. The mega-tool build_complete_character_slice also overlaps with nearly every other tool, and discover_ecosystem vs introspect_comfyui both probe local tooling, creating real selection ambiguity.
All names use a consistent gameforge_ prefix and snake_case, with action-first verbs for the majority (export_*, generate_*, init_*, lock_*, register_*, compute_*, define_*, compile_*, build_*). Minor deviations exist where a tool name is prefixed by the external tool instead of a verb (blender_rig_and_sockets, blender_ortho_turntable_bake, libresprite_cleanup_script), but the overall pattern is predictable.
At 24 tools the surface is on the heavy side, but the server genuinely spans a large end-to-end game art pipeline (discovery, style, rigging, baking, atlases, three engine exporters, audit), so most tools earn their place. It is close to the 25-tool 'heavy' threshold, making it slightly over-scoped but defensible.
Coverage is broad and includes create/init, generation workflows, three engine exporters, preview, and QA audit, forming a near-complete asset lifecycle. Gaps remain: there is no tool to list/inspect existing project assets or state beyond query_codex, and no delete/cleanup or update path for already-generated artifacts, which agents may need when iterating.