Gopeak vs Godot Forge
A side-by-side look at the Gopeak and Godot Forge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gopeak for gaming work as a local process; choose Godot Forge for gaming as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gopeak when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
GODOT_PATH, GOPEAK_TOOL_PROFILE, MCP_TOOL_PROFILE. - You want tools like
tool-catalog, project-list, project-info.
Choose Godot Forge when
- You need dedicated capabilities in the Gaming domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
godot_run_tests, godot_search_docs, godot_get_diagnostics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Gaming | Gaming |
| Quality signal | 63/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | GODOT_PATHGOPEAK_TOOL_PROFILEMCP_TOOL_PROFILE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 267 | 9 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 33 | 8 |
| Full listing | View Gopeak | View Godot Forge |
Tools & capabilities
Gopeak tools 33
tool-catalog[compact alias of tool_catalog] Discover available tools including hidden legacy tools. Use query to search by capability keywords. Results include group categorization (core/dynamic). Matching dynamic groups are auto-activated and become available immediately. Core groups (always visible): core_meta, core_project, core_editor, core_scene, core_script, core_class, core_signal, core_resource, core_export, core_runtime, core_visualizer, core_diagnostics. Dynamic groups (on-demand): scene_advanced, uid, import_export, autoload, signal, runtime, resource, animation, plugin, input, tilemap, audio, navigation, theme_ui, asset_store, testing, dx_tools, intent_tracking, class_advanced, lsp, dap, version_gate.project-list[compact alias of list_projects] Scans a directory for Godot projects (folders containing project.godot). Use to discover projects before using other tools. Returns array of {path, name}.project-info[compact alias of get_project_info] Returns metadata about a Godot project including name, version, main scene, autoloads, and directory structure. Use to understand project before modifying. Requires valid project.godot.project-search[compact alias of search_project] Searches for text or regex patterns across project files. Use to find function usages, variable references, or TODOs. Returns file paths and line numbers.project-setting-get[compact alias of get_project_setting] Reads a value from project.godot settings. Use to check game name, window size, physics settings, etc.project-setting-set[compact alias of set_project_setting] Writes a value to project.godot settings. Use to configure game name, window size, physics, etc.editor-launch[compact alias of launch_editor] Opens the Godot editor GUI for a project. Use when visual inspection or manual editing of scenes/scripts is needed. Opens a new window on the host system. Requires: project directory with project.godot file.editor-run[compact alias of run_project] Launches a Godot project in a new window and captures output. Use to test gameplay or verify script behavior. Runs until stop_project is called. Use get_debug_output to retrieve logs.editor-stop[compact alias of stop_project] Terminates the currently running Godot project process. Use to stop a project started with run_project. No effect if no project is running.editor-debug-output[compact alias of get_debug_output] Retrieves console output and errors from the currently running Godot project. Use after run_project to check logs, errors, and print statements. Returns empty if no project is running.editor-status[compact alias of get_editor_status] Returns the connection status of the Godot Editor Plugin bridge. Use to check if the editor is connected before using scene/resource tools that require the editor plugin.editor-version[compact alias of get_godot_version] Returns the installed Godot engine version string. Use to check compatibility (e.g., Godot 4.4+ features like UID). Returns version like "4.3.stable" or "4.4.dev".- +21 more on the listing page
Godot Forge tools 8
godot_run_testsRun 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.godot_search_docsSearch 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_diagnosticsGet LSP diagnostics (errors, warnings) from Godot's built-in language server. Requires Godot editor to be running with the project open.godot_analyze_sceneParse .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_scriptAnalyse 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_projectLaunch, stop, or get debug output from a running Godot project. Captures stdout/stderr with timestamps.godot_screenshotCapture a viewport screenshot from the running Godot project. Returns base64-encoded PNG image. Requires a display server (not headless mode).godot_get_project_infoReturn project structure overview: project name, Godot version, scenes, scripts, autoloads, addons, and directory tree. Uses progressive disclosure — summary by default, full details on request.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gopeak
{
"mcpServers": {
"gopeak": {
"command": "npx",
"args": [
"-y",
"gopeak"
],
"env": {
"GODOT_PATH": "YOUR_GODOT_PATH_HERE",
"GOPEAK_TOOL_PROFILE": "YOUR_GOPEAK_TOOL_PROFILE_HERE",
"MCP_TOOL_PROFILE": "YOUR_MCP_TOOL_PROFILE_HERE"
}
}
}
}
Godot Forge
{
"mcpServers": {
"gregario-godot-forge": {
"command": "npx",
"args": [
"-y",
"godot-forge"
]
}
}
}
Frequently asked questions
Gopeak is categorized under Gaming and uses a local stdio subprocess. Godot Forge belongs to Gaming and uses a local stdio subprocess. Pick Gopeak for gaming work and Godot Forge for gaming.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Gopeak is listed as free. Auth: no auth required. Godot Forge is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gopeak and gregario-godot-forge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gopeak has a quality signal of 63/100 (Good) with 1 views, 0 installs and 267 GitHub stars. Godot Forge has 61/100 (Good) with 5 views, 0 installs and 9 GitHub stars.