How coding-solo/godot-mcp works
Godot MCP exposes Godot project and editor operations as tools to an MCP-compatible AI client. The client requests a tool; the server either runs a direct Godot CLI command or delegates complex scene/resource work to the bundled GDScript operations script. Project discovery and analysis, runtime control and diagnostics, scene editing, and UID management are distinct capabilities. The README documents these branches; the sampled TypeScript excerpts do not show every handler implementation or its exact command wiring.
Main entry points: index.ts Godot MCP server · godot_operations.gd Godot operations
Components 12
MCP interface
- Godot MCP server
src/index.ts
Project insight
- Project discovery
src/index.ts - Project analysis
src/index.ts
Execution and diagnostics
- Editor and runtime
src/index.ts - Debug output
src/index.ts - Godot version
src/index.ts
Project editing
- Scene management
src/index.ts - UID management
src/index.ts - Godot operations
src/scripts/godot_operations.gd
Other components
- AI MCP client
- Godot engine
- Godot project files
Connections 15
- AI MCP client → Godot MCP server: requests tools
- Godot MCP server → Project discovery: dispatches
- Godot MCP server → Project analysis: dispatches
- Godot MCP server → Editor and runtime: dispatches
- Godot MCP server → Debug output: dispatches
- Godot MCP server → Godot version: dispatches
- Godot MCP server → Scene management: dispatches
- Godot MCP server → UID management: dispatches
- Godot MCP server → Godot engine: runs CLI commands
- Godot MCP server → Godot operations: invokes complex operations
- Project discovery → Godot project files: searches
- Project analysis → Godot project files: reads structure
- Scene management → Godot project files: edits resources
- UID management → Godot project files: reads and updates
- Godot operations → Godot engine: runs in engine