GoPeak MCP
An MCP server for Godot 4: the agent builds scenes and scripts, runs the game, reads errors and the debugger and pulls free assets
- 270 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent runs the Godot project and scripts and can edit and delete scene and resource files
- The runtime addon allows inspection of the running game and input injection
- The asset group downloads files from third-party providers over the network
Install
- Works in
Manual install
npx -y gopeakNeeds Godot 4.x and Node.js 18 or newer. For a global install use npm install -g gopeak.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent runs the Godot project and scripts and can edit and delete scene and resource files
- The runtime addon allows inspection of the running game and input injection
- The asset group downloads files from third-party providers over the network
This is third-party code. Review the repository files before installing.
What it does
GoPeak is a TypeScript MCP server for Godot 4. The agent finds projects, creates and edits scenes, nodes, scripts and resources, runs the game, reads debug output and fixes the first error right away. It starts with `npx -y gopeak`, and the client config only needs the path to Godot in `GODOT_PATH`. The compact profile is on by default: the list keeps the core tools while the rest sit in dynamic groups that activate on demand. The agent searches with `tool.catalog` and the matching group activates itself, `tool.groups` activates a group by hand, and the server tells the client that the list changed. The groups cover scenes, signals, animations, tilemaps, audio, navigation, UI themes, input, autoloads, import and export. The full and legacy profiles expose the whole list at once, delivered in pages of 33 tools. Some groups need extras. The editor addon is needed for scene edits through the bridge, the runtime addon for live inspection and screenshots, and the LSP on port 6005 and the DAP debugger on port 6006 give GDScript completion, breakpoints and call stacks. The `install-addon.sh` script installs the addons. A separate group searches and downloads free CC0 assets. The author labels the maturity of each group, and some still carry the audit-required status: they need checks on Godot 4 test projects.
Who it is for. For Godot 4 game developers who want to give Claude Code, Cursor or Cline access to a real project: scenes, running and debugging.
Good fit when
- You need a scene with a CharacterBody2D root and a movement script from a text description
- The game crashes: the agent runs the project, reads the output and fixes the first error
- You need debugging with breakpoints and call stacks through DAP
- You need free CC0 assets that the agent finds and adds to the project
- You want to save tokens: the compact profile does not load hundreds of tool descriptions at once
Not a fit when
- You work on Godot 3: the server targets Godot 4.x
- You only want GDScript hints: the server drives a project and does no teaching
- You need guaranteed results from groups marked audit-required: the author asks to verify them on Godot 4 test projects
- You cannot install addons into the project: without them the scene bridge, live inspection and screenshots are unavailable
Example request
Create `scenes/Player.tscn` with a CharacterBody2D root, add a movement script, run the project and fix the first errorMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
GODOT_PATHrequired- Path to the Godot executable
GOPEAK_TOOL_PROFILE- Tool profile: compact, full or legacy, compact by default
GOPEAK_TOOLS_PAGE_SIZE- Page size of the tool list, 33 by default
Limitations
You need Godot 4.x and Node.js 18 or newer, and the Godot path goes into `GODOT_PATH`. The compact profile is on by default, and the remaining tools open by groups. The runtime, testing, lsp and dap groups work only when the runtime addon, the editor, the LSP on port 6005 or DAP on port 6006 is running. The `asset_store` group calls asset providers over the network. The author marked many groups as needing verification, so go by their maturity labels. `gopeak setup` edits bash and zsh rc files only when run explicitly, and installing the package adds no hooks.
How to disable. Remove the godot block from the client config and run `npm uninstall -g gopeak` if you installed it globally. Turn off the addon plugins in Project Settings, Plugins and delete their folders from the project.
FAQ
How do I connect GoPeak to Claude Code or Cursor?
Add an MCP server to the config: command npx, arguments -y and gopeak, the `GODOT_PATH` variable and optionally `GOPEAK_TOOL_PROFILE`. Good first prompts: list projects in a folder, create a scene with a script, run the project and fix the top error.
How does the compact profile differ from full?
Compact shows a core toolset and the rest turn on by groups through tool.catalog or tool.groups, so fewer tokens are spent. The full and legacy profiles expose the whole list at once, delivered in pages of 33 tools, and `GOPEAK_TOOLS_PAGE_SIZE` changes the page size.
Do I need addons in the Godot project?
Not for basic operations. The `godot_mcp_editor` addon is needed by tools that work through the scene and resource bridge, and the runtime addon is needed for live inspection and screenshots. The `install-addon.sh` or install-addon.ps1 script runs in the project folder, and then you enable the plugins in Project Settings.
How do I get debugging with breakpoints?
The dap group needs the Godot debugger on port 6006 and the lsp group needs the language server on port 6005. The agent switches them on with tool.groups and gets breakpoints, stepping and call stacks.
What does gopeak setup do?
It adds hooks for update notifications to bash and zsh rc files. They are optional: installing the package adds no hooks, and you run the command explicitly.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server and plugin for Godot 4.4+: the agent edits scenes and scripts in the editor, runs the game and reads errors
An MCP server for the Godot engine: launch the editor, run projects and edit scenes from an agent
An MCP server with 157 tools for Godot 4: the agent edits scenes and projects, runs the game, changes live nodes and writes GDScript and .NET scripts
An MCP server for Godot 4 that runs inside the editor: the agent edits scenes, nodes and scripts, runs the project and reads the debugger, no Node.js
A .NET addon lets an agent drive the Godot editor: scenes, nodes, scripts, viewport screenshots and queries in the RQL language
An MCP server for the Godot engine: connects Claude Code, Claude Desktop and Codex to a live editor to build scenes, scripts and materials
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| GoPeak (this entry) | no | not required | 270 | |
| Godot MCP Full Control | no | not required | 506 | 157 tools for Godot 4 without dynamic groups or profiles |
| Godot MCP Native | no | not required | 863 | runs inside the Godot editor and needs no Node.js |
| Godot AI | yes | API key | 3,271 | connects Claude Code, Claude Desktop and Codex to a live editor |
README in short
The README opens with a three-minute quick start: requirements, running through npx, the client config and first prompts. It then explains tool profiles and dynamic groups with maturity labels, paged tool lists, installation options, addons, capabilities by area and documentation links. The localized READMEs are shorter than the English one.