godot-mcp
Related Servers
Alternatives to godot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables 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 assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.4714MIT
- AlicenseDqualityAmaintenanceEnables Blender automation via MCP with 107 tools for complex mesh modeling, PBR texturing, UV mapping, rigging, animation, lighting, rendering, and a pre-export curing pipeline for Godot 4.x/Redot GLB export.107GPL 3.0
- 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.-
- AlicenseCqualityBmaintenanceEnables AI assistants to interact with the Godot Engine editor and projects, including scene editing, script management, physics queries, and asset operations.1261MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to create and modify Godot game engine projects by managing scenes, generating GDScript code, creating animations, and controlling the Godot editor through natural language commands.143 npm1MIT
TDQS
Scored across 28 tools
Each tool targets a distinct action-resource pair: project lifecycle, scene editing, animation graph generation, camera work, and diagnostics are cleanly separated. Even similar animation/camera tools (e.g., generate_state_machine vs compile_state_transitions) have clearly different purposes and arguments.
All tool names follow a consistent verb_first_snake_case pattern (launch_editor, get_godot_version, run_project, generate_track_filter, batch_shader_uniforms). Verb choices are generally descriptive and uniform, with no camelCase or mixed naming conventions.
With 28 tools, the server exceeds the 25+ threshold for 'too many' and would overwhelm an agent. While Godot is a broad domain, many tools are highly specialized (e.g., quantize_animation_keyframes, generate_bezier_camera_path) and could be consolidated or scoped down.
The server heavily favors creation/generation workflows but lacks basic editing operations like node deletion, scene tree inspection, property updates, or script file creation. This causes dead-ends: users can add nodes but not list or remove them, and cannot update existing scene resources beyond saving.