The Godot MCP Bridge server enables AI assistants (Claude, Cursor, Copilot, etc.) to control and interact with the Godot 4 game editor through 168+ tools, allowing game development via natural language commands.
Connection Management
Connect/disconnect/check status of the WebSocket bridge to a running Godot editor
Send custom low-level commands via godot_command as an escape hatch
Project Management
Read/write project settings, browse filesystem trees, search files by pattern
Convert between UIDs and res:// paths, get autoload and metadata info
Scene Operations
Create, open, save, delete, play, and stop scenes
Get scene hierarchy (editor and runtime), instance scenes as child nodes
Node Manipulation
Add, delete, duplicate, rename, reparent, and update properties on nodes
Attach resources, set Control anchor presets, manage signals and groups
Full Undo/Redo support on all mutations
Script Management
List, read, create, edit, attach, and validate GDScript files
Search text across project files, list scripts open in the editor
Editor Interaction
Capture editor/game viewport screenshots, execute GDScript in editor or game context
Read error/output logs, clear console, reload plugins or the entire project
Input Simulation
Simulate keyboard events, mouse clicks/movement, and Godot Input actions
Run input sequences with delays, record and replay input sessions
List, create, and update input actions
Runtime Game Inspection & Modification
Read/set runtime node properties (single or batch), get the runtime scene tree
Execute scripts in game context, capture frames, monitor property values over time
Find UI elements, click buttons by text, wait for nodes to appear, navigate actors
Animation System
List, create, and remove animations in AnimationPlayer
Add tracks, set keyframes, get detailed animation info
TileMap Operations
Set, get, fill, and clear tile cells; get tilemap metadata and list used cells
Theme & UI Styling
Create theme resources, set color/constant/font size/StyleBox overrides
Performance & Profiling
Get real-time performance monitor values (FPS, memory, physics, rendering)
Get editor performance summaries and analyze scene complexity
Batch & Analysis
Find nodes by class type, script, or signal connections
Batch-get/set properties across multiple nodes, inspect all signals and connections
Key Features
Smart type parsing for Godot types (Vector2, Color, booleans, etc.)
Auto 2D/3D detection for physics, audio, and navigation nodes
Built-in presets for lighting, particles, shaders, and audio effects
JSON-RPC 2.0 over WebSocket bridge protocol
Provides 168 AI-powered tools for the Godot 4 Editor, enabling AI assistants to build games with natural language by creating scenes, editing scripts, simulating input, and analyzing running games.
Integrates with Godot 4.2+ editor via WebSocket bridge, providing 168 tools across 25 categories for scene manipulation, script editing, animation, physics, audio, and game testing through AI assistants.
Runs the TypeScript MCP server that bridges AI clients to the Godot editor plugin, handling communication between AI assistants and Godot's WebSocket server.
Supports SVG textures in Godot scenes through the update_property tool, allowing AI assistants to set SVG files as textures on nodes like Sprite2D.
Used to implement the MCP server that bridges AI clients to the Godot editor plugin, providing the tool definitions and WebSocket communication layer.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Godot MCP Bridge add a player node to the current scene"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
168 AI-powered tools for the Godot 4 Editor — connect your AI assistant (Claude, Cursor, Cline, Copilot) to Godot and build games with natural language.
Connect your AI assistant to Godot in under 5 minutes.
Copy addons/godot_mcp/ into your Godot project. Enable it in Project > Project Settings > Plugins. The plugin starts a WebSocket server inside the editor automatically.
cd server
npm install && npm run buildThis compiles the TypeScript MCP server that bridges your AI client to the Godot plugin.
Add the server to your AI client's MCP config. Open Godot, and your AI assistant now has real-time access to 168 tools — creating scenes, editing scripts, simulating input, and analyzing your running game.
Related MCP server: godot-mcp
Add to .claude/mcp.json:
{
"mcpServers": {
"godot": {
"command": "node",
"args": ["/absolute/path/to/server/dist/index.js"]
}
}
}Add to .vscode/mcp.json:
{
"servers": {
"godot": {
"command": "node",
"args": ["./server/dist/index.js"]
}
}
}node server/dist/index.jsThe server communicates over stdio (stdin/stdout) using the MCP protocol.
cd server
npm run runThis will automatically:
Build the MCP server
Detect project.godot in parent folders (or GODOT_PROJECT_PATH)
Sync addon to addons/godot_mcp
Enable plugin in project.godot
Create MCP config files
Sync AI context files
# | Category | Tools | Highlights |
1 | Project | 7 | Settings read/write, UID conversion |
2 | Scene | 9 | Create, open, play, stop, instance, save |
3 | Node | 14 | Add/delete/rename/move with UndoRedo, signals, groups |
4 | Script | 8 | CRUD, attach, validate, search with line numbers |
5 | Editor | 10 | Screenshots, execute GDScript, error log, reload |
6 | Input | 7 | Keyboard, mouse, action simulation, sequences |
7 | Runtime | 19 | Game inspection, frame capture, recording/replay, UI |
8 | Animation | 6 | CRUD, tracks, keyframes |
9 | AnimationTree | 8 | State machine, transitions, blend tree |
10 | TileMap | 6 | Cell operations (TileMapLayer for Godot 4.3+) |
11 | 3D Scene | 6 | Mesh primitives, .glb import, lighting presets, PBR |
12 | Physics | 6 | Auto 2D/3D collision, raycasts, layers |
13 | Particles | 5 | GPU particles + fire/smoke/rain/snow/sparks presets |
14 | Navigation | 6 | Region, agent, bake, pathfinding |
15 | Audio | 6 | Player (auto 2D/3D), bus effects chain |
16 | Theme/UI | 6 | StyleBoxFlat, color/constant/font overrides |
17 | Shader | 6 | Templates (canvas_item, spatial, particles, sky) |
18 | Resource | 6 | .tres CRUD, autoload management |
19 | Batch | 8 | Find by type, bulk set, dependency analysis |
20 | Testing | 6 | Automated scenarios, assertions, stress testing |
21 | Analysis | 4 | Scene complexity, signal flow, unused resources |
22 | Profiling | 2 | FPS, memory, physics, rendering monitors |
23 | Export | 3 | Preset listing, build commands |
Total | 168 | + 4 core connection tools |
No need to construct complex objects manually. Property values auto-convert:
"Vector2(100, 200)" → Vector2(100, 200)
"Color(1, 0, 0)" → Color(1, 0, 0)
"#ff0000" → Color(1, 0, 0)
"Color.RED" → Color(1, 0, 0)
"true" → true
"42" → 42Every add_node, delete_node, update_property, rename_node, and move_node goes through Godot's UndoRedo system. Your users can Ctrl+Z any AI action.
Physics bodies, collision shapes, audio players, particles, and navigation nodes automatically detect whether the parent is 2D or 3D — the right type is created every time.
Lighting: sun, indoor, dramatic, spot
Particles: fire, smoke, rain, snow, sparks
Shaders: canvas_item, spatial, particles, sky templates
Audio effects: reverb, delay, compressor, EQ, distortion, chorus, phaser
AI: godot_connect
AI: create_scene path="res://scenes/level.tscn" rootType="Node2D"
AI: add_node type="CharacterBody2D" name="Player" parentPath="."
AI: add_node type="Sprite2D" name="Sprite" parentPath="Player"
AI: update_property path="Player/Sprite" property="texture" value="res://icon.svg"
AI: setup_collision path="Player" shapeType="rectangle" size="Vector2(32, 32)"
AI: create_script path="res://scripts/player.gd" content="extends CharacterBody2D..."
AI: attach_script nodePath="Player" scriptPath="res://scripts/player.gd"
AI: save_scene
AI: play_scene
AI: simulate_key key="Space"
AI: get_game_screenshot
AI: stop_sceneserver/src/
├── index.ts TypeScript MCP server (stdio transport)
├── toolCatalog.ts 168 tool definitions with input schemas
└── godotBridge.ts WebSocket client → Godot editor
addons/godot_mcp/
├── plugin.gd Plugin entry point
├── websocket_server.gd Local WebSocket server (port 6505)
├── command_router.gd Loads 20 handler modules, dispatches commands
└── commands/
├── base_commands.gd Shared utilities (type parser, undo, I/O)
├── type_parser.gd Smart string→Godot type conversion
├── undo_helper.gd UndoRedo wrapper
├── core_commands.gd Project, scene, node, script, editor (47 handlers)
├── editor_commands.gd Screenshots, execute script (4)
├── input_commands.gd Input simulation (7)
├── runtime_commands.gd Game inspection & UI (15)
├── animation_commands.gd Animation CRUD (6)
├── animation_tree_commands.gd State machine & blend tree (8)
├── tilemap_commands.gd Tile operations (6)
├── scene3d_commands.gd 3D scene building (6)
├── physics_commands.gd Physics & collision (6)
├── particles_commands.gd GPU particles + presets (5)
├── navigation_commands.gd Nav regions & pathfinding (6)
├── audio_commands.gd Audio players & bus effects (6)
├── theme_commands.gd Theme & UI styling (6)
├── shader_commands.gd Shader management (4)
├── resource_commands.gd Resource & autoload (6)
├── batch_commands.gd Batch operations (8)
├── testing_commands.gd Testing & QA (5)
├── analysis_commands.gd Code analysis (4)
├── profiling_commands.gd Performance profiling (2)
└── export_commands.gd Export management (3)JSON-RPC 2.0 over WebSocket (ws://127.0.0.1:6505):
→ { "jsonrpc": "2.0", "id": 1, "method": "add_node", "params": { "type": "Sprite2D", "name": "Player" } }
← { "jsonrpc": "2.0", "id": 1, "result": { "tool": "add_node", "data": { "path": "/root/Main/Player" } } }Override bridge URL: GODOT_WS_URL=ws://127.0.0.1:6505 node server/dist/index.js
Godot 4.2+ (4.3+ recommended for TileMapLayer)
Node.js 18+
Any MCP-compatible AI client
When deployed to a Godot project, these context files help AI assistants understand the available tools:
File | Purpose | Used by |
| Complete 168-tool reference with workflows | All AI agents |
| Architecture + capability summary | Codex, Gemini, agents |
| Quick reference + build commands | Claude Code |
| Copilot-specific instructions | GitHub Copilot |
Add animation track. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add audio bus. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add effect to audio bus. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add AudioStreamPlayer node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Register autoload singleton. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create GridMap node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add MeshInstance3D with primitive mesh. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add node with type and optional properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add RayCast2D or RayCast3D. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Attach resource to node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Instance scene as a child node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add AnimationTree state machine state. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add state machine transition. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Analyze scene complexity metrics. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Analyze signal graph in project. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Apply particle effect preset. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Assert node property value. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Assert screen text is visible. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Assign ShaderMaterial to node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Attach script to node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Read multiple node properties in batch. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Batch set property by filter. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Capture multiple game frames. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Clear output panel. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Click button by text content. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Compare screenshots. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Connect node signal. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create new animation. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create AnimationTree node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create GPUParticles2D or GPUParticles3D. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create resource file. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create a new scene file. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create a script file. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create shader file from template. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create theme resource. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set property across scenes. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Delete node from scene. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Delete a scene file. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Detect dependency cycles. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Disconnect node signal. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Duplicate node and children. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Edit resource properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Edit script with replace or full content. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Edit shader file. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Execute GDScript in editor context. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Execute script in game context. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get export command or trigger export. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find nearby nodes by position. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Search node references in files. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find runtime nodes by script. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find nodes by class type. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find nodes in a group. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find script references. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find signal connections. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find UI elements in game. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Find unreferenced resources. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get animation details. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Inspect AnimationTree structure. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get audio bus layout. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get audio node information. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get autoload node details. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get collision shape information. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get editor errors and stack traces. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get editor performance summary. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Capture editor viewport screenshot. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get export configuration info. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get recursive file tree with optional filters. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Read runtime node properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get runtime scene hierarchy. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Capture running game screenshot. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
List input actions. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get node groups. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get node properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
List scripts open in editor. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get editor output log. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get particle system details. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get performance monitor values. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get collision layer and mask. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get project metadata and autoload information. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Read project settings. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get project statistics summary. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get resource preview thumbnail. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get scene dependencies. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Read raw .tscn content. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get scene hierarchy from editor/runtime. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get shader params from material. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Inspect node signals and connections. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get test report. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get theme override info. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Send a custom command to Godot bridge. This is a low-level escape hatch when a named tool is not enough.
Inputs: command (required), payload, timeoutMs, autoConnect.
Connect to a running Godot bridge over WebSocket.
Inputs: timeoutMs.
Disconnect from the Godot bridge.
Inputs: no named parameters.
Return current connection status to the Godot bridge.
Inputs: no named parameters.
List animations in AnimationPlayer. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
List export presets. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
List scripts in project. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Monitor property values over time. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Move or reparent node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Move actor to target. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Open a scene in editor. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Run scene from editor. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Convert res:// path to UID. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Read resource properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Read script file content. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Read shader file. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Reload plugin and reconnect bridge. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Rescan and reload project. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Remove animation. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Unregister autoload singleton. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Remove state machine state. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Remove state machine transition. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Rename node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Replay recorded input. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Run stress input test. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Run automated test scenario. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Save current scene. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Search files by pattern or glob. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Search text across files. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set anchor preset for Control node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set keyframe value. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Configure audio bus properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Configure blend tree node. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set multiple runtime node properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set runtime node property. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Create or update input action. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set StandardMaterial3D properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set node groups. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set particle color gradient. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Configure particle process material. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set collision layer and mask. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set a project setting value. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set shader uniform value. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set theme color override. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set theme constant override. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set theme font size override. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set theme stylebox override. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set AnimationTree parameter. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set Camera3D properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Add collision shapes. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Configure world environment. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set up lighting nodes. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Configure physics body properties. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Simulate Godot Input action. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Simulate keyboard input. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Simulate mouse click. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Simulate mouse movement. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Run input sequence with delays. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Start input recording. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Stop input recording. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Stop running scene. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Clear all tilemap cells. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Fill tile rectangle. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get tile cell data. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Get tilemap metadata. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
List used tile cells. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Set single tile cell. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Convert UID to res:// project path. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Update node property. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Validate script syntax. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Wait for node to appear. (Compatibility tool)
Inputs: timeoutMs, autoConnect.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 167 tools
With 167 tools, significant overlap exists between generic utilities (add_node) and specific variants (add_mesh_instance, add_audio_player). Multiple property accessors (get_node_properties, batch_get_properties, get_game_node_properties) operate in different contexts but have minimal descriptions that fail to clarify when to use each, causing high risk of misselection.
While predominantly using snake_case verb_noun patterns, inconsistencies emerge with tilemap_* prefixing, godot_* prefixing for connection tools, and mixed verb choices (add/create/remove/delete). Some tools use noun_verb ordering (uid_to_project_path) while others use verb_noun, and similar operations lack parallel structure (cross_scene_set_property vs batch_set_property).
At 167 tools, this vastly exceeds the 50+ threshold for extreme mismatch. Despite Godot's complexity, this quantity will overwhelm agent context windows and selection logic. A more coherent design would use fewer tools with parameters rather than discrete endpoints for every operation.
The set provides extensive coverage across Godot subsystems including scene management, scripting, animation, audio, physics, UI, and testing. While the granularity is inconsistent (some operations have specific tools while others rely on generic ones), there appear to be few functional gaps for core game engine workflows.
AI game maker: build, run, screenshot and play-test Godot and retro console games in a live project
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
Discover AI tools for game development — 100+ tools indexed by engine, task, and pricing.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
