Godot Forge
Run Godot 4 tests, query API docs, analyze scripts and scenes, and use LSP-aware helpers from your coding agent on a solo game project.
Overview
Godot Forge is a MCP server for the Build phase that connects AI agents to Godot 4 test runs, API docs, script analysis, scene parsing, and LSP-aware project context over stdio.
What is this MCP server?
- Godot 4 test runner exposed as MCP tools for agent-driven verification
- Embedded API documentation access for GDScript and engine classes
- Script analysis and scene parsing for safer refactors in chat-driven edits
- LSP-oriented tooling to align agent suggestions with project symbols
- Optional GODOT_PATH env var with auto-detect when unset (stdio npm godot-forge 0.1.2)
- Version 0.1.2 published as npm identifier godot-forge with stdio transport
- Documented environment variable GODOT_PATH (string, optional auto-detect)
- Repository: github.com/gregario/godot-forge
Community signal: 6 GitHub stars.
What problem does it solve?
Solo Godot developers lose velocity when agents hallucinate engine APIs and cannot run project tests or read .tscn structure from the IDE.
Who is it for?
One-person Godot 4 game shops using Claude Code or Cursor who want engine-native MCP tools instead of generic file grep.
Skip if: Teams on Unity or Unreal only, non-game SaaS products, or builders unwilling to install Godot 4.x locally.
What do I get? / Deliverables
After registering godot-forge, your agent can ground edits in Godot 4 docs, scenes, and tests so indie game loops ship with fewer broken scenes and mystery runtime errors.
- Agent-invokable Godot 4 test runs from the project workspace
- Structured script and scene introspection for safer AI edits
- In-session API doc lookups aligned with Godot 4.x
Recommended MCP Servers
Journey fit
Primary shelf is Build agent-tooling because Godot Forge is how solo game devs extend the IDE agent with Godot 4–specific analysis, docs, and tests. Agent-tooling captures test runner, script analysis, scene parsing, API docs, and LSP bridges—capabilities that shape how the agent edits Godot projects.
How it compares
Godot-specific dev MCP, not a generic GitHub Actions deploy skill or cloud game backend.
Common Questions / FAQ
Who is godot-forge for?
Indie and solo developers shipping Godot 4 games who want their AI coding agent to run tests, read scenes, and cite real engine APIs.
When should I use godot-forge?
Use it throughout Build agent sessions and before Ship when you need test runner, script analysis, scene parsing, docs, or LSP-backed context in MCP.
How do I add godot-forge to my agent?
Install npm package godot-forge 0.1.2 as a stdio MCP server, set GODOT_PATH if needed, restart your host, and confirm Godot 4 tools are listed.