In-depth architectural comparison of the Unity MCP and Godot Forge MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Unity MCP
Gaming · Local stdio
Quality: 56/100 (Good) | Auth: OAuth 2.0
Godot Forge
Gaming · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Unity MCP if you need specialized Gaming tools running via a local process. Choose Godot Forge if your workspace requires Gaming integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Unity MCP when:
You need dedicated capabilities in the Gaming domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
⃣ 🏠 🍎 🪟 🐧 - MCP Server for Unity Editor and for a game made with Unity
Godot 4 development companion with test running (GUT/GdUnit4), API docs with 3→4 migration mapping, script analysis, scene parsing, screenshots, and LSP diagnostics.
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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Unity MCP is categorized under Gaming and uses a local stdio subprocess. In contrast, Godot Forge belongs to Gaming using local stdio subprocess. Select Unity MCP when you need capabilities focused on gaming and Godot Forge when you require tools for gaming.
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.
godot_get_diagnostics
Get LSP diagnostics (errors, warnings) from Godot's built-in language server. Requires Godot editor to be running with the project open.
godot_analyze_scene
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).
godot_analyze_script
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.
godot_run_project
Launch, stop, or get debug output from a running Godot project. Captures stdout/stderr with timestamps.
godot_screenshot
Capture a viewport screenshot from the running Godot project. Returns base64-encoded PNG image. Requires a display server (not headless mode).
godot_get_project_info
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.