Godot 4 MCP server — test runner, API docs, script analysis, scene parsing, LSP.
Godot Forge MCP server exists for a simple reason — assistants are far more useful when they can act on Godot Forge directly instead of describing what you should do. Godot 4 MCP server — test runner, API docs, script analysis, scene parsing, LSP.
The server ships on npm as godot-forge, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Godot Forge is connected, these are the calls the assistant has available:
godot_run_tests — Run GUT/GdUnit4 tests, get structured pass/fail resultsgodot_search_docs — Search Godot 4 API docs with 3→4 migration mappinggodot_analyze_script — Detect 10 GDScript pitfalls (deprecated API, coupling, re-entrancy)godot_analyze_scene — Parse .tscn/.tres, detect antipatterns and format errorsgodot_get_project_info — Project structure overview with progressive disclosuregodot_get_diagnostics — LSP diagnostics from Godot's language servergodot_run_project — Launch/stop project, capture debug outputgodot_screenshot — Capture viewport screenshot as base64 PNGDevelopment — The Development tool exposed by this serverYou will need one environment variable: GODOT_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
npx execution - Godot 4.x: auto-detected (optional for 6 of 8 tools) - Any MCP-compatible IDE: Claude Code, Cursor, VS Code, Windsurf, Zed, and moreThis sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Godot Forge's toolset — godot_run_tests, godot_search_docs, godot_analyze_script and 6 more — is a fair guide to whether it matches your workflow. It is maintained by gregario; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Godot Forge's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| godot_run_tests | Run GUT/GdUnit4 tests, get structured pass/fail results |
| godot_search_docs | Search Godot 4 API docs with 3→4 migration mapping |
| godot_analyze_script | Detect 10 GDScript pitfalls (deprecated API, coupling, re-entrancy) |
| godot_analyze_scene | Parse .tscn/.tres, detect antipatterns and format errors |
| godot_get_project_info | Project structure overview with progressive disclosure |
| godot_get_diagnostics | LSP diagnostics from Godot's language server |
| godot_run_project | Launch/stop project, capture debug output |
| godot_screenshot | Capture viewport screenshot as base64 PNG |
| Development | The Development tool exposed by this server. |
{
"mcpServers": {
"godot-forge": {
"command": "npx",
"args": ["-y", "godot-forge"],
"env": {
"GODOT_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
npx execution - Godot 4.x: auto-detected (optional for 6 of 8 tools) - Any MCP-compatible IDE: Claude Code, Cursor, VS Code, Windsurf, Zed, and more| Variable | Description | Required |
|---|---|---|
| GODOT_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.