add_node
Add a node to an existing scene
LABSCO SUMMARY
The run, read-the-error, fix loop closes without alt-tabbing.
run_project captures what the project prints, get_debug_output reads it while it is running, and stop_project ends it — so an agent acts on the real error text instead of a description of it. Scene construction is covered as far as nodes, sprites and MeshLibrary exports; anything past that is still editor work.
What it is
Control over Godot and a project on disk: the editor launched, a project or a single scene run with its output captured, projects listed and inspected, and scenes, nodes and MeshLibrary exports created.
What you get
- A project run — all of it, or one scene — with its output and errors captured, and stopped again
- The debug output and errors read while it runs
- Godot projects in a directory listed, recursively if you ask, and any project's metadata read
- Scenes created with a root node type, nodes added with a type, parent path and properties, sprites loaded into a Sprite2D, and the scene saved, optionally to a new path
- A scene exported as a MeshLibrary resource containing the mesh items you name
- UID handling for Godot 4.4 and later: a file's UID read, and a project's UID references updated by resaving its resources
- The installed Godot version reported
Requirements
npx on your PATH and Godot installed — the server launches the editor and runs the project through it. Every project call takes the path to the project.
Setup effort
One command — npx @coding-solo/godot-mcp
USE CASES
01
Chasing a runtime error in a scene
Run just the scene that misbehaves, read the debug output while it runs, and stop it once you have the error. The loop stays in one place.
02
Scaffolding a scene's node tree
Create the scene with its root type, add the nodes under their parents with the properties they need, load the sprite, and save.
03
Working out what a project you inherited needs
List the projects in the directory, read the metadata of the one you care about, and check the Godot version installed against what it expects.
04
Repairing UID references after a move
Read the UID for the file in question and resave the project's resources so the references point where they should — the Godot 4.4 and later path.
05
Exporting a MeshLibrary for a GridMap
Name the mesh items and export the scene as a MeshLibrary resource to the output path, which is the step a GridMap workflow keeps needing.
14 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_scene
Create a new Godot scene file
export_mesh_library
Export a scene as a MeshLibrary resource
get_debug_output
Get the current debug output and errors
get_godot_version
Get the installed Godot version
get_project_info
Retrieve metadata about a Godot project
get_uid
Get the UID for a specific file in a Godot project (for Godot 4.4+)
launch_editor
Launch Godot editor for a specific project
list_projects
List Godot projects in a directory
load_sprite
Load a sprite into a Sprite2D node
run_project
Run the Godot project and capture output
save_scene
Save changes to a scene file
stop_project
Stop the currently running Godot project
update_project_uids
Update UID references in a Godot project by resaving resources (for Godot 4.4+)
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools when we connected.
Requires
- npx on PATH
- Node.js
- DEBUG in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"godot": {
"command": "npx",
"args": [
"@coding-solo/godot-mcp"
],
"env": {
"DEBUG": "true"
},
"disabled": false,
"autoApprove": [
"launch_editor",
"run_project",
"get_debug_output",
"stop_project",
"get_godot_version",
"list_projects",
"get_project_info",
"create_scene",
"add_node",
"load_sprite",
"export_mesh_library",
"save_scene",
"get_uid",
"update_project_uids"
]
}
}
}npx
TERMINAL
npx @coding-solo/godot-mcp
