Godot Forge
NPM · GODOT-FORGE · SCANNED SEP 20
Godot 4 MCP server — test runner, API docs, script analysis, scene parsing, LSP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 146 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1005 tokens (~125/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Godot Forge MCP server?
Godot Forge runs locally as an npm package, launched with npx -y godot-forge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · godot-forge
claude mcp add gregario-godot-forge -- npx -y godot-forge
{
"mcpServers": {
"gregario-godot-forge": {
"command": "npx",
"args": [
"-y",
"godot-forge"
]
}
}
} {
"servers": {
"gregario-godot-forge": {
"command": "npx",
"args": [
"-y",
"godot-forge"
]
}
}
} codex mcp add gregario-godot-forge -- npx -y godot-forge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gregario-godot-forge": {
"type": "local",
"command": [
"npx",
"-y",
"godot-forge"
],
"enabled": true
}
}
} openclaw mcp add gregario-godot-forge --command npx --arg -y --arg godot-forge
mcp_servers:
gregario-godot-forge:
command: "npx"
args: ["-y", "godot-forge"] {
"McpServers": {
"gregario-godot-forge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"godot-forge"
]
}
}
} assistant mcp add gregario-godot-forge -t stdio -c npx -a -y godot-forge
{
"mcpServers": {
"gregario-godot-forge": {
"command": "npx",
"args": [
"-y",
"godot-forge"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/godot-forge@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
godot_analyze_scene ~94
Parse .tscn scene files or .tres resource files and return structured analysis. Detects antipatterns (deep nesting, oversized scenes, missing scripts) and format errors (preload in .tres, custom class names in type field, integer resource IDs).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to .tscn or .tres file (e.g., res://scenes/main.tscn) |
No output schema declared.
No examples provided.
godot_analyze_script ~96
Analyse GDScript files for all 10 battle-tested pitfalls: Godot 3→4 API misuse, giant scripts, := on Variant, tight coupling, signal re-entrancy, autoload misuse, missing signal disconnect, _init() timing, Python-isms, and static func on autoloads.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to .gd file (e.g., res://scripts/player.gd) |
No output schema declared.
No examples provided.
godot_get_diagnostics ~84
Get LSP diagnostics (errors, warnings) from Godot's built-in language server. Requires Godot editor to be running with the project open.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | File path to get diagnostics for (e.g., scripts/player.gd). Omit for project-wide. |
| port | number | – | LSP port (default: 6005) |
No output schema declared.
No examples provided.
godot_get_project_info ~81
Return project structure overview: project name, Godot version, scenes, scripts, autoloads, addons, and directory tree. Uses progressive disclosure — summary by default, full details on request.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Level of detail: 'summary' (default) for counts and top-level dirs, 'full' for complete file listings |
No output schema declared.
No examples provided.
godot_run_project ~66
Launch, stop, or get debug output from a running Godot project. Captures stdout/stderr with timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| scene | string | – | Scene to launch directly (e.g., res://scenes/main.tscn) |
No output schema declared.
No examples provided.
godot_run_tests ~136
Run GUT or GdUnit4 tests headlessly and return structured pass/fail results. Auto-detects the test framework. Returns total/passed/failed counts with failure details including file paths and line numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Force specific framework (auto-detected if omitted) |
| inner_class | string | – | Filter to specific inner test class |
| method | string | – | Filter to specific test method name |
| script_path | string | – | Filter to specific test script (e.g., res://tests/test_inventory.gd) |
| timeout | number | – | Timeout in seconds (default: 60) |
No output schema declared.
No examples provided.
godot_screenshot ~70
Capture a viewport screenshot from the running Godot project. Returns base64-encoded PNG image. Requires a display server (not headless mode).
| Name | Type | Req | Description |
|---|---|---|---|
| scene | string | – | Scene to capture (e.g., res://scenes/main.tscn). If omitted, captures the project's main scene. |
No output schema declared.
No examples provided.
godot_search_docs ~96
Search Godot 4.x API documentation. Returns class overviews, method details, or fuzzy search results. Automatically detects Godot 3 API queries and suggests Godot 4 equivalents — the #1 source of AI-generated GDScript bugs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Class name (e.g., 'CharacterBody2D'), method (e.g., 'CharacterBody2D.move_and_slide'), or search term |
No output schema declared.
No examples provided.
What is the Godot Forge MCP server?
Godot Forge is an MCP server listed in the public MCP registry as io.github.gregario/godot-forge. Godot 4 MCP server, test runner, API docs, script analysis, scene parsing, LSP. This page covers its npm package (godot-forge).
Is the Godot Forge MCP server safe to use?
Godot Forge scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Godot Forge MCP server expose?
Godot Forge exposes 8 tools: godot_run_tests, godot_search_docs, godot_get_diagnostics, godot_analyze_scene, godot_analyze_script, and 3 more. Their descriptions and schemas cost roughly 723 tokens of context every time the server is loaded.
Is the Godot Forge MCP server still maintained?
Godot Forge is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Godot Forge MCP server under?
Godot Forge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.