Godot Forge
Related Servers
Alternatives to Godot Forge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect, edit, and run Godot 4 projects — scenes, nodes, signals, resources, animations, tile maps, audio buses, visual shaders, project settings, input actions, and exports — with GDScript language-server diagnostics, offline class reference, live in-game debugging, and GUT/GdUnit4 test runs. It works through a live editor bridge so every edit can be undone with Ctrl+Z, and falls back to headless execution when the editor is closed.1MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to automate Godot 4 projects via headless tooling, live editor control, and runtime remote control, including scene building, testing, and observation.431MIT
- AlicenseAqualityCmaintenanceEnables AI coding assistants to directly control a running Godot editor for autonomous game development, including scene building, tilemap and animation manipulation, UI automation, and live GDScript execution.46MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read and edit Godot 4.x scenes and resources, introspect the class API, run the game in a managed headless process with frame stepping, input injection and screenshots, validate scripts, and diagnose code via a built-in GDScript LSP plus a bridge to an already open editor.23MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to build, run, and debug Godot projects by editing scenes and scripts, inspecting live game state, injecting input, capturing viewports, and examining native debugger state through 42 tools.European Union Public 1.2
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Godot game projects through real-time error detection, automated testing, code analysis, and safe git-based patching. Provides comprehensive project context and development workflow automation for Godot developers.MIT
TDQS
Scored across 29 tools
Most tools target clearly distinct Godot subsystems (files vs. script vs. resource, run vs. game vs. test, project vs. editor). A few boundaries are slightly soft — e.g. editing a .gd file can be done via files.edit or script.edit — but the descriptions consistently clarify which tool to prefer.
Tool names are consistently lowercase single nouns (signal, scene, node, physics, navigation, etc.) with no camelCase/snake_case mixing. Minor deviations are the plural forms (files, changes, tiles, particles, assets) and the concatenated 'world3d' instead of 'world_3d'.
29 tools is heavy for an MCP surface and risks selection paralysis. Each tool does cover a distinct subsystem and bundles many actions, so the count is borderline rather than purely excessive for an editor-automation server of this scope.
The surface covers project setup, file/scene/node/script/resource lifecycles, signals, animation, tiles, physics, navigation, 3D world building, shaders, UI, audio, particles, asset generation/import, testing, and export. Gaps such as dedicated multiplayer or localization tools are minor relative to the editor-automation domain.