A
licenseC
qualityD
maintenanceEnables AI assistants to interact with and manipulate Godot game engine projects, including creating projects, launching editor, managing scenes and nodes.
12
722 npm
1
MIT
Godot MCP
by mcintalmo
Related Servers
Alternatives to Godot MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to fully access and manipulate Godot editor projects, including scenes, scripts, nodes, and settings, with an interactive visualizer.443MIT
- AlicenseNot gradedqualityBmaintenanceEnables compatible AI clients to query and edit game projects through native editor APIs, covering scenes, nodes, components, properties, assets, prefabs, preview, logs, and builds.1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.10027MIT
- AlicenseCqualityCmaintenanceEnables AI agents to interact with the Godot game engine, including project inspection, scene/script parsing, headless exports, runtime control with live scene-tree inspection and evaluation, and API documentation search.100722 npm4MIT
- AlicenseAqualityBmaintenanceEnables 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
TDQS
C2.7/5.0
Scored across 126 tools
Disambiguation4/5
Most tools target a distinct subsystem and action, making selection fairly clear even at this scale. A few near-overlaps exist, such as set_editor_selection vs set_selected_nodes and get_node_signals vs get_signal_connections, but the descriptions generally prevent serious confusion.
Naming Consistency5/5
All tools follow a consistent godot_ prefix with snake_case verb_noun naming, such as create_node, modify_node, and bake_navmesh. Minor exceptions like godot_undo and godot_lsp_query still fit a predictable pattern and do not break overall consistency.
Tool Count1/5
126 tools is an extreme count that far exceeds reasonable agent-facing surface area, even for a large domain like Godot. The sheer number will bloat context, increase selection overhead, and likely deserves splitting into focused sub-servers.
Completeness4/5
The tool surface covers an unusually broad range of Godot workflows: scene editing, scripting, rendering, physics, audio, UI testing, multiplayer, assets, and export. Minor gaps exist, such as no direct script/scene file deletion or renaming and no generic method invocation, but most workflows have workable paths.
Maintenance
ActivityStale
ResponsivenessNo issues