@coding-solo/godot-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 2 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @coding-solo/godot-mcp@0.1.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 0 returned a result.
get_debug_output | No usable answer tool reported an error: No active Godot process. Possible solutions: - Use run_project to start a Godot project first - Check if the Godot process crashed unexp |
get_godot_version | No usable answer tool reported an error: Failed to get Godot version: spawn /usr/bin/godot ENOENT Possible solutions: - Ensure Godot is installed correctly - Check if the GODOT_ |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
launch_editor projectPath
Launch Godot editor for a specific project
run_project projectPath, scene
Run the Godot project and capture output
get_debug_output
Get the current debug output and errors
stop_project
Stop the currently running Godot project
get_godot_version
Get the installed Godot version
9 more tools
list_projects directory, recursive
List Godot projects in a directory
get_project_info projectPath
Retrieve metadata about a Godot project
create_scene projectPath, scenePath, rootNodeType
Create a new Godot scene file
add_node projectPath, scenePath, parentNodePath, nodeType, nodeName, properties
Add a node to an existing scene
load_sprite projectPath, scenePath, nodePath, texturePath
Load a sprite into a Sprite2D node
export_mesh_library projectPath, scenePath, outputPath, meshItemNames
Export a scene as a MeshLibrary resource
save_scene projectPath, scenePath, newPath
Save changes to a scene file
get_uid projectPath, filePath
Get the UID for a specific file in a Godot project (for Godot 4.4+)
update_project_uids projectPath
Update UID references in a Godot project by resaving resources (for Godot 4.4+)
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18.0.0 |
| Source | github.com/Coding-Solo/godot-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-tSwmKN5D3JWGfnyPFxijxjdsT+GKIQrf9g6zYNefLvOVYx2UTC9PhyFFHc9vphtjyFrtjYf1n5Vq1zRNN3UXBA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40coding-solo/godot-mcp)
New version out? Ask for a fresh report.