Godot MCP Server

Scene construction and GDScript maintenance sit alongside project inspection in godot-mcp. Developers can examine a scene's node hierarchy, add or reparent nodes, attach scripts, connect signals, and reuse existing scenes as instances. Script tools support targeted edits and syntax validation, while file searches and Godot ClassDB queries help inspect usages and available engine APIs. Resource operations cover collision shapes, textures, meshes, and materials; SVG artwork can also be rendered into PNG assets.

The listed runtime tools support a testing sequence: launch a scene, inspect live nodes, send input, capture the viewport, review errors, and stop execution. Input injection, screenshots, and live node queries require a running game with the MCPRuntime helper connected. For broader navigation, the browser visualizer maps script relationships and exposes variables, functions, and signals, with code changes synchronized to Godot. Project settings, input bindings, and autoload registrations can also be managed. Operation is local to a single Godot instance, and changes save directly without undo.