Install Asset
Install via Godot
To maintain one source of truth, Godot Asset Library is just a mirror of the old asset library so you can download directly on Godot via the integrated asset library browser
Quick Information
AI coding assistants are blind when working in game engines. They can edit code, but they can't see what the game actually looks like, can't inspect the scene tree, can't check if their changes broke something visually, and can't control the editor. They're writing code into a void and hoping it works.AI Essentials Toolkit fixes that. It runs a lightweight HTTP server inside the Godot editor that gives any AI assistant Claude, ChatGPT, Copilot, Cursor, or custom tools direct access to:Screenshots: Capture the editor viewport or the running game in one call. The AI can actually see what the game looks like after every change instead of guessing.Scene Tree Inspection: Dump the full node hierarchy. The AI knows exactly what nodes exist, their types, and how they're structured. Property Read/Write: Read all properties on any node, or change them live in the editor. Position, color, scale, visibility β no manual inspector clicking. Game Control: Startand stop the game programmatically. Run it, screenshot, verify, stop, fix, repeat. Script Validation: Check every GDScript file for parse errors in one call. Catch broken scripts before running.Two servers work together: an editor plugin (port 7777) for scene editing, and a game autoload (port 7778) that captures the actual running game viewport. Any tool that can make HTTP requests can use it, no special SDK, no proprietary integration.The result: AI assistants go from blindly predicting code to iterating visually. Edit a UI, screenshot, see it's wrong, fix it, screenshot again. That loop is what makes the difference between an AI that breaks things and one that actually ships.
AI Essentials Toolkit for Godot 4
Give AI coding assistants eyes and hands inside the Godot editor. Screenshots, scene inspection, property editing, game control, and script validation β all via a simple HTTP API.
Works with any AI tool that can make HTTP requests: Claude, ChatGPT, GitHub Copilot, Cursor, or your own scripts.
Features
| Endpoint | Method | Description |
|---|---|---|
/ping |
GET | Check connection, engine version, game state |
/screenshot |
GET | Capture editor viewport (auto-redirects to game when running) |
/screenshot/editor |
GET | Always capture editor 3D viewport |
/scene/tree |
GET | Full scene node hierarchy |
/scene/node |
POST | Get all properties of a node |
/scene/set |
POST | Set a node property in the editor |
/run |
POST | Run the main scene (F5) |
/stop |
POST | Stop the running game |
/parse |
GET | Check all GDScript files for errors |
Two Servers
- Editor Server (port 7777) β Runs as an EditorPlugin, always available when the editor is open
- Game Server (port 7778) β Runs as an autoload inside the game, captures the actual game viewport
Installation
From Godot Asset Library
- Open Godot β AssetLib tab β Search "AI Essentials Toolkit" β Install
From GitHub
- Download/clone this repo
- Copy the
addons/ai_essentials_toolkit/folder into your project'saddons/directory - Go to Project β Project Settings β Plugins and enable "AI Essentials Toolkit"
- Add the game server autoload: Project β Project Settings β Autoload β Add
addons/ai_essentials_toolkit/game_server.gdwith nameAIToolkitGameServer
Usage
Quick Test
With the editor open and plugin enabled, run:
curl http://localhost:7777/ping
Screenshot
curl http://localhost:7777/screenshot
# Returns: {"path": "C:/Users/.../ai_toolkit_screenshot.png", "source": "editor_3d_viewport"}
Scene Inspection
curl http://localhost:7777/scene/tree
# Returns full node hierarchy
curl -X POST http://localhost:7777/scene/node -d '{"path": "Camera3D"}'
# Returns all properties of the node
Set Property
curl -X POST http://localhost:7777/scene/set -d '{"path": "Camera3D", "property": "fov", "value": 90}'
Game Control
curl -X POST http://localhost:7777/run # Start game
curl -X POST http://localhost:7777/stop # Stop game
Game Screenshot (while game is running)
curl http://localhost:7778/screenshot
# Returns: {"path": "...", "source": "running_game"}
Parse Check
curl http://localhost:7777/parse
# Returns: {"total_scripts": 40, "errors": [], "ok": true}
Integration Examples
With Claude CLI / Copilot CLI
The toolkit includes a ready-made CLI extension. Copy extensions/godot-dev/extension.mjs to your Copilot extensions directory:
~/.copilot/extensions/godot-dev/extension.mjs
With Any AI Tool
Any tool that can call HTTP endpoints can use this. Point it at http://localhost:7777 and use the endpoints above.
With Python
import requests, json
# Take screenshot
r = requests.get("http://localhost:7777/screenshot")
data = r.json()
print(f"Screenshot at: {data['path']}")
# Get scene tree
r = requests.get("http://localhost:7777/scene/tree")
print(r.json()["tree"])
Requirements
- Godot 4.4+
- No external dependencies
License
MIT License β see LICENSE
AI coding assistants are blind when working in game engines. They can edit code, but they can't see what the game actually looks like, can't inspect the scene tree, can't check if their changes broke something visually, and can't control the editor. They're writing code into a void and hoping it works.
AI Essentials Toolkit fixes that. It runs a lightweight HTTP server inside the Godot editor that gives any AI assistant Claude, ChatGPT, Copilot, Cursor, or custom tools direct access to:
Screenshots: Capture the editor viewport or the running game in one call. The AI can actually see what the game looks like after every change instead of guessing.
Scene Tree Inspection: Dump the full node hierarchy. The AI knows exactly what nodes exist, their types, and how they're structured.
Property Read/Write: Read all properties on any node, or change them live in the editor. Position, color, scale, visibility β no manual inspector clicking.
Game Control: Startand stop the game programmatically. Run it, screenshot, verify, stop, fix, repeat.
Script Validation: Check every GDScript file for parse errors in one call. Catch broken scripts before running.
Two servers work together: an editor plugin (port 7777) for scene editing, and a game autoload (port 7778) that captures the actual running game viewport. Any tool that can make HTTP requests can use it, no special SDK, no proprietary integration.
The result: AI assistants go from blindly predicting code to iterating visually. Edit a UI, screenshot, see it's wrong, fix it, screenshot again. That loop is what makes the difference between an AI that breaks things and one that actually ships.
Reviews
Quick Information
AI coding assistants are blind when working in game engines. They can edit code, but they can't see what the game actually looks like, can't inspect the scene tree, can't check if their changes broke something visually, and can't control the editor. They're writing code into a void and hoping it works.AI Essentials Toolkit fixes that. It runs a lightweight HTTP server inside the Godot editor that gives any AI assistant Claude, ChatGPT, Copilot, Cursor, or custom tools direct access to:Screenshots: Capture the editor viewport or the running game in one call. The AI can actually see what the game looks like after every change instead of guessing.Scene Tree Inspection: Dump the full node hierarchy. The AI knows exactly what nodes exist, their types, and how they're structured. Property Read/Write: Read all properties on any node, or change them live in the editor. Position, color, scale, visibility β no manual inspector clicking. Game Control: Startand stop the game programmatically. Run it, screenshot, verify, stop, fix, repeat. Script Validation: Check every GDScript file for parse errors in one call. Catch broken scripts before running.Two servers work together: an editor plugin (port 7777) for scene editing, and a game autoload (port 7778) that captures the actual running game viewport. Any tool that can make HTTP requests can use it, no special SDK, no proprietary integration.The result: AI assistants go from blindly predicting code to iterating visually. Edit a UI, screenshot, see it's wrong, fix it, screenshot again. That loop is what makes the difference between an AI that breaks things and one that actually ships.