godot-ai-mcp
Related Servers
Alternatives to godot-ai-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to launch and control the Godot editor, run projects, capture debug output, inspect project structure, and manage scenes, nodes, and UIDs through MCP tools. It provides a direct feedback loop for debugging and code generation in Godot projects.14143 npmMIT
- 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.288 npmMIT
- 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
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect, author, debug, simulate, and visually verify Godot 4.x projects through standard MCP tools, including scene editing, runtime control, and viewport capture.143 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to edit, run, inspect, and fix Godot 4 projects through an MCP server with dynamic tool groups and setup-gated capabilities.163 npm264MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to directly run, inspect, modify, and debug Godot game development projects through 110+ tools covering scenes, scripts, resources, runtime debugging, and asset management.3321 npm2MIT
TDQS
Scored across 21 tools
Each tool targets a distinct operation (e.g., add_node vs remove_node, create_scene vs save_scene, read_script vs write_script). No two tools appear to have overlapping purposes.
All tool names follow a consistent verb_noun pattern in snake_case, using clear, imperative verbs like get, list, set, create, add, remove, etc. No mixing of conventions.
21 tools is well-scoped for Godot game engine operations, covering scene editing, node manipulation, scripting, project management, and debugging without being overwhelming or sparse.
Core CRUD operations for scenes, nodes, and scripts are present, along with debugging and project management. Minor gaps exist (e.g., no scene deletion, no resource management beyond sprite loading), but the surface is largely complete.