Godot AI
Related Servers
Alternatives to Godot AI
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceConnects MCP-capable AI clients to a running Godot 4 editor for scene, node, project, and debug runtime operations via a local-first architecture.361MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.10022MIT
- FlicenseAqualityAmaintenanceMCP server that connects AI coding assistants to a live Godot editor, enabling scene, node, script, resource, runtime, debugger, and test workflows through natural language.45-
- AlicenseCqualityCmaintenanceEnables AI-driven game development by providing MCP tools to interact with the Godot editor, including scene editing, node manipulation, script attachment, and scene execution.2813 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides a secure, authenticated MCP bridge to control a local Godot editor from Cursor, enabling scene/node management, script validation, editor diagnostics, and runtime inspection through a whitelisted set of tools.MIT
- FlicenseAqualityDmaintenanceProvides AI assistants with tools to launch the Godot editor, run projects, manipulate scenes, manage scripts, and control node properties through a standardized MCP interface.21-
TDQS
Scored across 47 tools
Most tools have clearly distinct domains (scene, node, script, resource, animation, material, particles, camera, audio, tilemap, gridmap, navigation, CSG), and the _manage suffix groups related ops. However, there is some overlap: editor_state vs editor_manage(op=state), scene_get_hierarchy vs scene_manage(get_roots), and script_create/script_patch/script_manage vs filesystem_manage(write_text) all have partially redundant surfaces that could cause misselection.
The naming is mostly verb_noun (project_run, scene_open, node_create, script_attach, batch_execute) with a consistent _manage suffix for multi-op tools. But there are deviations: editor_screenshot and editor_reload_plugin break the pattern, some tools use noun_verb (editor_screenshot, project_run) while others use noun_manage, and the _manage tools mix verbs inside ops (e.g. settings_get vs get_class vs list). The pattern is readable but not fully uniform.
47 tools is a very large surface for a single MCP server. While the Godot editor is a broad domain, many tools are actually multi-op wrappers (e.g. project_manage, node_manage, resource_manage) that bundle dozens of operations, making the effective surface even larger. This exceeds the typical well-scoped range and will burden agent tool selection.
The tool surface is remarkably comprehensive for Godot editor automation: scene lifecycle, node manipulation, scripts, resources, materials, animations, particles, cameras, audio, tilemaps, gridmaps, navigation, CSG, UI, themes, input, signals, autoloads, tests, project settings, and runtime game control. There are no obvious dead ends; even niche areas like VisualShader and custom addon tools are covered.