Godotwright

Godotwright Big worlds. Better code. Keep creating.

MCP server, CLI and Claude Code plugin for Godot 4.7. Works with Claude Code, Codex, Cursor, VS Code, Gemini CLI and any MCP client. No editor needed.

Website · Install in your agent · Reference · 3D models · Benchmark · Changelog

Concept artwork. Explore the toolkit, real demo and model gallery on the website .

Real output (godotwright 0.1.0). Watch as video

And 3D models from code, no Blender: 59 ready-made kinds. See the gallery

Coding agents learned Godot from years of Godot 3 tutorials. They write yield, export var and KinematicBody2D, invent methods, and wire signals to nodes that are not in the scene. Godotwright is the check between the agent and your project: the real Godot 4.7 API offline, a scored review of every script, headless Godot runs, and safe edits. It works from files, so it needs no open editor, and it works fine next to an editor-driving MCP server.

Without and with

Quickstart

1. Review your game. Nothing to install:

npx -y godotwright review ~/games/my-game

You get a score from 0 to 100 for api, performance, quality and structure, and each finding as res://player.gd:12: error [rule] message with the Godot 4 fix. No Godot install needed.

2. Give it to your agent. In Claude Code:

/plugin install godotwright --marketplace laaielichter/Godotwright

3. Ask for something. For example: *"Review the project and fix what Godotwright finds."* Every Godot file Claude edits is now reviewed right after the edit, and its errors go straight back to Claude.

Install in your agent

Run the agent from the Godot project folder, or pass --project . --tier premium gives full detail for large models; --tier cheap (the default) gives short output and step-by-step instructions for small ones. Needs Node.js 22.12+.

New in 0.6.0

• Shaders. godot_shader reviews every shader against Godot 4.7's own shader tables (Godot 3 names, built-ins in the wrong place, read-only built-ins written, colours without source_color) and compiles it with Godot headless, which finds every language error without a GPU; gpu: true also draws it, for what only the driver rejects.
• The real build. godot_export_run exports headless, reads the .pck without Godot, checks it against what the game loads, runs it, and makes patch packs that carry only what changed.
• Scene integrity. Duplicate, invalid and stale uids, broken resource ids and edits Godot drops on the next editor save, found from the files and repaired by godot_fix across files.
• Proof that stays. godot_scenario keeps a passing play run as a regression test; screenshot steps in scenarios and named baselines, compared with moved areas and blank pictures named; JUnit XML for your CI's test tab; godot_leaks names what grows per cycle and where it is made.
• Upgrades. Godot 4.6 and 4.7 changes as review rules and fixes, target for a project on an older 4.x, and compare_godot to see what a 4.8 beta breaks.
• Resources and imports. godot_resource_edit edits .tres files and import settings and verifies the reimport.
• For agents and teams. Tool sets (--tools core is about a third of the tool list), --read-only, structured results, progress and cancel for long Godot runs, and protected folders that no write may touch.

0.5.0 brought godot_code (Godot's own GDScript language server: warnings at the project's levels, inferred types, definitions and completion, also for unsaved code), shader compilation by drawing (godotwright shaders, godot_check shaders: true) and visual tests with screenshot baselines; see the changelog.

All changes: CHANGELOG.md.

What it does

Check. review scores your scripts and scenes without Godot: Godot 3 code, unknown classes, methods and signals, missing $Node paths, scene connections to missing methods, unknown input actions, per-frame lookups, static typing. api answers from the official Godot 4.7 class reference (1078 classes), offline. check runs Godot headless and reports each error once, as file:line.

Change. rename a function, signal, node or file everywhere; project edits settings, input actions and autoloads; scene adds nodes, sets properties, connects signals and attaches scripts. Each one checks names and types against Godot 4.7, shows a dry run first and touches only its own lines. migrate ports Godot 3 scripts to Godot 4 where that is mechanical (more on porting).

Run and see. test runs GUT or GdUnit4 tests and prints only what failed; play runs a scene, presses the keys you give on the frames you give, and prints the values you watch; screenshot renders a scene or a model to a PNG.

Build 3D models. model build makes a clean .glb with no Blender: one of 59 ready-made kinds (vehicles, aircraft, ships, buildings, plants, terrain with lakes and rivers) or your own JSON spec. model identify says what a thing is (parts, sizes, pivots), model view draws it as text for agents that cannot see pictures, and model lint scores it.

Review every pull request. Add this to your game's repository:

# .github/workflows/godotwright.yml

on: pull_request permissions: { contents: read, pull-requests: write } jobs: receipt: runs-on: ubuntu-latest steps:

• uses: actions/checkout@v5
• uses: laaielichter/godotwright@v0.5.0 with: { comment: "true" }

It downloads a checksum-verified Godot, runs the review, the check and your tests, and posts the result as a comment. No editor, no GPU. review-only: "true" skips Godot. Inputs, SARIF and plain CI: GDScript review in CI.

Learn. Rules that real Godot keeps contradicting turn into hints, findings you mark as wrong stay hidden, and lessons you add come back when the same error does. All of it stays on your machine; sharing anonymous counts is opt-in and off by default (PRIVACY.md).

Every command, option and rule: docs/reference.md.

The 38 tools

All MCP tools (most are also CLI commands; --tools core loads 13)

| godot_lessons | Lessons from real Godot projects (sym