Godot MCP Server
Related Servers
Alternatives to Godot MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConnects Claude directly to Godot 4 projects to read and manipulate scenes, nodes, scripts, and assets within the editor. It enables real-time scene tree management, script editing, and resource configuration through a local Node.js bridge and GDScript plugin.16775 npmMIT
- FlicenseCqualityDmaintenanceEnables AI assistants to control Godot game engine projects through a WebSocket bridge. Supports scene editing, node manipulation, script management, and project introspection via 163 registered tools.1001-
- AlicenseAqualityDmaintenanceMCP bridge between an AI assistant and the Godot editor, enabling control via 6 tools (call methods, run GDScript, screenshots, etc.) over WebSocket.1018 npm3MIT
- AlicenseNot gradedqualityBmaintenanceLet Claude, Cursor, or any MCP-compatible AI work inside your Godot project: read and edit scenes, write and validate scripts, run the game, drive it, and read the errors — without copy-pasting anything.10MIT
- FlicenseNot gradedqualityDmaintenanceBridges AI assistants with the Godot 4 editor, exposing tools to inspect scenes, create nodes, modify properties, capture screenshots, debug scripts, and manage project files via the Model Context Protocol.-
- 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
TDQS
Scored across 167 tools
The set spans many distinct Godot domains, but there are many parallel editor-vs-running-game variants and multiple performance/analysis tools with close boundaries (e.g., get_node_properties vs get_game_node_properties, get_game_performance vs get_performance_monitors vs get_editor_performance). Descriptions help clarify intent, but the sheer volume increases the chance of tool misselection.
Nearly all tools use snake_case and predictable verb/resource wording, which keeps names readable. However, some names lead with a domain/tool prefix (e.g., tilemap_set_cell, game_...) while others lead with the verb, so the pattern is not perfectly uniform.
167 tools is far beyond a reasonable MCP tool surface and is an extreme mismatch for practical tool selection, even for a broad Godot editor/runtime integration. The count creates significant cognitive overload and makes discovery and correct invocation difficult.
Coverage is very broad: filesystem, scenes, nodes, scripts, editor/runtime control, animation, audio, shaders, exports, resources, input, 3D/physics/navigation, particles, testing, themes, tilemaps, and Android deployment are all represented. Some lifecycle gaps remain, such as scene deletion/duplication, audio playback control, richer UI-control creation, and asset import workflows.