Launch Godot editor for a specific project

Run the Godot project and capture output

Get the current debug output and errors

Stop the currently running Godot project

Get the installed Godot version

List Godot projects in a directory

Retrieve metadata about a Godot project

Create a new Godot scene file

Add a node to an existing scene

Load a sprite into a Sprite2D node

Export a scene as a MeshLibrary resource

Save changes to a scene file

Get the UID for a specific file in a Godot project (for Godot 4.4+)

Update UID references in a Godot project by resaving resources (for Godot 4.4+)

Get information about the test harness capabilities and game project

Get a snapshot of game state including available autoloads, constants, and configuration

Validate that a test scenario configuration is valid before running it

Check if a unit, building, or resource scene exists and get its properties

Validate that all unit/building scene paths exist for a race

Run the game with test harness mode enabled for a specific scenario

Check MLX local LLM server health and Apple Silicon platform compatibility

Get the hierarchical node tree of a scene file as JSON

Remove a node from a scene and save

Set one or more properties on an existing node and save the scene

Create a new GDScript file with optional content or default template

Attach an existing GDScript to a node in a scene

Recursively list all .gd scripts in the project or a subdirectory

Render a scene headlessly via --script and capture a PNG. Best for standalone scenes without autoload deps. For real game scenes, prefer test_take_screenshot against a running game.

Capture a screenshot of the currently running game via file-based IPC with TestController. Requires the game to already be running (use run_project or test_run_scenario first). Works with autoloads and real scenes.