godot-test-mcp
MCP server for automated Godot 4 game testing. Launch games, capture errors, verify changes — all from Claude Code or any MCP client.
Features (Phase 1)
- Launch & Stop: Run Godot projects in headless or windowed mode
- Error Capture: Parse and categorize GDScript errors, parse errors, resource failures
- One-Shot Verify:
godot_run_and_check— launch, run N seconds, report PASS/FAIL - Headless Import: Quick parse-check without running the game
Quick Start
-
Clone:
git clone https://github.com/hyunlord/godot-test-mcp.git
-
Install:
cd godot-test-mcp pip install -e .
-
Add to your Godot project's
.mcp.json:{ "mcpServers": { "godot-test": { "command": "python3", "args": ["/path/to/godot-test-mcp/src/server.py"], "env": { "GODOT_PROJECT_PATH": ".", "GODOT_PATH": "" } } } }
-
In Claude Code:
godot_run_and_check(seconds=15)
Tools
| Tool | Description |
|---|---|
godot_launch |
Start Godot (headless/windowed/editor) |
godot_stop |
Stop running Godot process |
godot_get_errors |
Get parsed errors/warnings |
godot_get_output |
Get raw stdout/stderr |
godot_run_and_check |
Launch → run N sec → collect errors → PASS/FAIL |
godot_headless_import |
Quick --headless --quit parse check |
godot_get_status |
Check if Godot is running/stopped/crashed |
Environment Variables
| Variable | Description |
|---|---|
GODOT_PATH |
Path to Godot executable (auto-detected if empty) |
GODOT_PROJECT_PATH |
Path to Godot project root (auto-detected if empty) |
Godot Auto-Detection
If GODOT_PATH is not set, the server searches in order:
- macOS:
/Applications/Godot.app/Contents/MacOS/Godot,~/Applications/... - Linux:
/usr/bin/godot, snap/flatpak paths - Windows:
C:\Godot\Godot.exe,%LOCALAPPDATA%\Godot\... PATHlookup viawhich godot
Project Auto-Detection
If GODOT_PROJECT_PATH is not set, the server searches for project.godot starting from the current directory and walking up to 5 parent directories.
Roadmap
- Phase 1: Launch + error capture (current)
- Phase 2: Tick control + entity state query (WebSocket)
- Phase 3: Cheat commands + assertions
- Phase 4: Rust/GPU profiling
- Phase 5: CI/CD integration
License
MIT
Metadata
Release files for godot-test-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| godot_test_mcp-0.1.0.tar.gz | 18.3 kB | Without provenance | Details for godot_test_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| godot_test_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for godot_test_mcp-0.1.0-py3-none-any.whl |
Total release size: 30.7 kB
Release files / godot_test_mcp-0.1.0.tar.gz
| Download URL | godot_test_mcp-0.1.0.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f24b3d89f7cfdfcf4f86fcec4dfa051eecd9cd0fd99b83dd2341ed38eca27255
|
|
BLAKE2b-256 checksum How to use checksums |
abe6cf5d143ec285b88c63ba9a3bcb59c471f183f2b9668ff491d2d711462210
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / godot_test_mcp-0.1.0-py3-none-any.whl
| Download URL | godot_test_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c79828c22794ff5e71d2c20ef04369591b80ab6c758c3ac4ae38f76986ccc2e
|
|
BLAKE2b-256 checksum How to use checksums |
c32595e836e0be50efc167383b356c863adbfbe78733f6ac9c50a5258c1bd19c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for godot-test-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.