Godot Forge MCP Server

<h1 align="center">Godot Forge</h1> The MCP server for Godot 4. Test runner, API docs, script analysis, and more.

---

AI coding assistants are structurally bad at GDScript. Models trained on data skewed towards Godot 3 hallucinate deprecated APIs (yield instead of await, KinematicBody instead of CharacterBody3D, export var instead of @export var). Godot Forge fixes this.

8 tools. Zero config. Works with every MCP-compatible IDE.

<a href="https://glama.ai/mcp/servers/gregario/godot-forge"> </a>

Install

npx -y godot-forge

That's it. Godot Forge auto-detects your Godot binary (Steam, Homebrew, direct download) and finds your project.godot automatically.

Add to your IDE

<details open> <summary><strong>Claude Code</strong></summary>

claude mcp add godot-forge -- npx -y godot-forge

</details> <details> <summary><strong>Cursor</strong></summary>

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "godot-forge": {
      "command": "npx",
      "args": ["-y", "godot-forge"]
    }
  }
}

</details> <details> <summary><strong>VS Code (Copilot)</strong></summary>

Add to .vscode/mcp.json:

{
  "servers": {
    "godot-forge": {
      "command": "npx",
      "args": ["-y", "godot-forge"]
    }
  }
}

</details> <details> <summary><strong>Windsurf</strong></summary>

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "godot-forge": {
      "command": "npx",
      "args": ["-y", "godot-forge"]
    }
  }
}

</details> <details> <summary><strong>Zed</strong></summary>

Add to settings.json:

{
  "context_servers": {
    "godot-forge": {
      "command": {
        "path": "npx",
        "args": ["-y", "godot-forge"]
      }
    }
  }
}

</details> <details> <summary><strong>Claude Desktop</strong></summary>

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "godot-forge": {
      "command": "npx",
      "args": ["-y", "godot-forge"]
    }
  }
}

</details> <details> <summary><strong>More IDEs (Codex, Gemini CLI, JetBrains, Continue, Cline, Roo Code, Neovim, OpenCode, Kiro)</strong></summary>

See IDE Setup Guide for configuration snippets for all supported IDEs.

</details>

Tools

Tool	Description	Needs Godot	Needs Editor
godot_run_tests	Run GUT/GdUnit4 tests, get structured pass/fail results	Yes	No
godot_search_docs	Search Godot 4 API docs with 3→4 migration mapping	No	No
godot_analyze_script	Detect 10 GDScript pitfalls (deprecated API, coupling, re-entrancy)	No	No
godot_analyze_scene	Parse .tscn/.tres, detect antipatterns and format errors	No	No
godot_get_project_info	Project structure overview with progressive disclosure	No	No
godot_get_diagnostics	LSP diagnostics from Godot's language server	No	Yes
godot_run_project	Launch/stop project, capture debug output	Yes	No
godot_screenshot	Capture viewport screenshot as base64 PNG	Yes	No

[!TIP] 6 of 8 tools work without Godot installed. Only test running, project launching, and screenshots need the binary.

Features

Test Runner

Auto-detects GUT and GdUnit4. Returns structured JSON with pass/fail counts, failure details with file paths and line numbers. Supports filtering by script, method, or inner class.

Ask your AI: "Run the water profile tests"
→ { total: 5, passed: 5, failed: 0, duration_ms: 462 }

Godot 3→4 Migration Mapping

The #1 reason AI writes broken GDScript. When your AI queries a deprecated API, it gets the correct Godot 4 equivalent instantly (30+ mappings covering classes, methods, syntax, and constants).

Query: "KinematicBody"  →  "Renamed to CharacterBody3D in Godo