Godot Forge — Godot 4 MCP server for Claude Code and other IDEs
An MCP server that gives your coding assistant eight Godot 4 tools: test runs, API lookup, GDScript and scene checks, LSP diagnostics.
claude mcp add --env GODOT_PATH=<GODOT_PATH> --transport stdio godot-forge -- npx -y godot-forgeWhat Godot Forge does
Ask an assistant for GDScript and you often get Godot 3 code back: yield where await belongs, KinematicBody instead of CharacterBody3D, export var instead of @export var. Godot Forge answers those lookups with the Godot 4 form. The mapping covers more than 30 entries across classes, methods, syntax and constants.
Eight tools ship with the server. godot_run_tests finds GUT or GdUnit4 on its own and returns JSON with pass and fail counts plus file paths and line numbers; you can narrow a run to one script, method or inner class. godot_analyze_script reports ten GDScript pitfalls, among them deprecated API calls, long get_node("../../...") chains and signal re-entrancy. godot_analyze_scene reads .tscn and .tres files, godot_get_project_info outlines the project, and godot_get_diagnostics pulls real compiler errors from Godot's language server.
Six of the eight tools run without Godot installed. Tests, project launch and screenshots need the binary; LSP diagnostics also need the editor open on your project. The server looks for Godot in GODOT_PATH first, then godot or godot4 on PATH, then Steam and platform default locations. Keep Godot somewhere unusual and the binary stays invisible until you set GODOT_PATH.
What it helps with
- run GUT or GdUnit4 suites and see which tests failed
- swap deprecated Godot 3 calls for their Godot 4 equivalents
- scan a script for ten common GDScript mistakes
- check a
.tscnfile for deep nesting and broken references - pull real compiler errors from Godot's language server
Example prompts for the agent
- Run the water profile tests and show me the failures
- Check
player.gdfor deprecated Godot 3 API - Parse
main.tscnand flag anything nested too deep
How to install Godot Forge
Platform CLI
claude mcp add --env GODOT_PATH=<GODOT_PATH> --transport stdio godot-forge -- npx -y godot-forgeReplace <…> with your own values
Platform CLI
codex mcp add godot-forge --env GODOT_PATH=<GODOT_PATH> -- npx -y godot-forgeReplace <…> with your own values
Config file
{
"mcpServers": {
"godot-forge": {
"command": "npx",
"args": [
"-y",
"godot-forge"
],
"env": {
"GODOT_PATH": "<GODOT_PATH>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"godot-forge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"godot-forge"
],
"env": {
"GODOT_PATH": "<GODOT_PATH>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e GODOT_PATH=<GODOT_PATH> godot-forge npx -y godot-forgeReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Godot Forge
How do I install Godot Forge in Claude Code?
Run claude mcp add godot-forge -- npx -y godot-forge. If your Godot binary is in a custom location, pass it instead: claude mcp add --env GODOT_PATH=<GODOT_PATH> --transport stdio godot-forge -- npx -y godot-forge.
What does Godot Forge do?
It hands your assistant eight Godot 4 tools: test running, API search with Godot 3 to 4 mapping, script and scene analysis, project structure, LSP diagnostics, project launch and viewport screenshots.
Do I need Godot installed to use it?
Not for six of the eight tools. The binary is required for test runs, launching the project and screenshots, and LSP diagnostics additionally need the Godot editor open with your project.
