Log inSubmit server
Gopeak logo

Gopeak

GoPeak connects AI assistants to Godot 4.x projects for editing, execution, inspection, and debugging.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Gopeak

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "gopeak": {
      "command": "npx",
      "args": [
        "-y",
        "gopeak"
      ],
      "env": {
        "GODOT_PATH": "YOUR_VALUE_HERE",
        "GOPEAK_TOOL_PROFILE": "YOUR_VALUE_HERE",
        "MCP_TOOL_PROFILE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 33 tools correctly (21d ago).

Overview

The gopeak MCP server connects AI assistants to Godot 4.x projects through tools for project discovery, scene and script editing, runtime inspection, testing, and debugging. It runs through Node.js and can expose a compact, dynamically activated tool surface or the full legacy list. Reach for it when an agent needs feedback from an actual Godot project, including logs, runtime state, LSP, or DAP debugging. Some capabilities require Godot addons, editor services, runtime sockets, or specific Godot versions.

Use cases

  • Create and modify Godot scenes and scripts
  • Run projects and inspect debug output
  • Activate LSP tools for GDScript assistance
  • Use DAP tools for breakpoints and stack traces
  • Capture runtime screenshots and viewport state

Key features

  • Godot 4.x project editing
  • Compact dynamic tool groups
  • Full and legacy tool profiles
  • Runtime inspection and testing
  • Optional LSP and DAP integration
  • Cursor-based tool-list pagination

Tools33

What Gopeak lets your agent do. Expand a tool for its parameters.

Verified live~6.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

26/26 checks healthy over the last 90d

What it can do

From the 33 tools this server returned when we ran it.

Can delete or modify data · 1Makes network requests · 1Read-only tools · 32
Network at startup3 connections
Files written at startupNone
Install scriptsprepare, postinstall
npm provenanceNot published
Package age240 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · gopeak (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars272Stargazers on the source repository.
npm downloads765Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed33Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Gopeak works

What the gopeak MCP server does

The gopeak MCP server gives an MCP-compatible AI client access to Godot 4.x project workflows. It can help an agent find projects, inspect project information, create or edit scenes, modify scripts and resources, run a project, read debug output, and investigate errors. The repository describes a broad tool surface covering project work, scene and resource operations, runtime inspection, testing, asset workflows, LSP, and DAP.

This makes gopeak relevant to the Developer Tools category, especially for developers who want an assistant to work against a real project rather than only generate detached code. Example workflows include creating a CharacterBody2D scene, running the game, checking its output, and addressing the highest-priority error.

How it works

GoPeak is launched as a Node.js process and communicates with an MCP client over the configured server connection. The quick-start command is npx -y gopeak; a global npm installation is also supported. Godot 4.x and Node.js 18 or newer are listed as requirements.

The default compact profile exposes a trusted core and activates additional tool groups when needed. A client or agent can search the catalog with tool.catalog, activate a group with tool.groups, and reset active groups when the work is complete. The server sends notifications/tools/list_changed after tool availability changes, allowing clients such as Claude Code and Claude Desktop to refresh their tool list. Clients that do not refresh automatically may need to reconnect or trigger another tools-list request.

The full profile exposes the complete legacy tool list, while legacy preserves the same exposed behavior for older configurations. Tool-list responses use cursor-based pagination rather than returning every tool in one response.

Setup and configuration

Run the gopeak MCP server with:

Terminal
npx -y gopeak

Alternatively, install it globally with npm install -g gopeak and start it using gopeak. Add the process to an MCP client configuration and set GODOT_PATH to the Godot executable or installation path used by the client. GOPEAK_TOOL_PROFILE selects the exposure profile; compact is the default. MCP_TOOL_PROFILE is available as a fallback alias.

The optional gopeak setup command configures update-notification shell hooks. It only changes supported bash or zsh rc files when explicitly run; npm installation does not install those hooks automatically.

Tools and capabilities

Available capability groups include:

  • Project discovery, project health checks, scaffolding, error logs, and usage searches.
  • Scene, node, script, resource, animation, navigation, audio, UI theme, input, and TileMap workflows.
  • Runtime inspection, screenshots, viewport capture, and input injection when the required runtime support is available.
  • GDScript completions, hover information, and symbols through LSP on port 6005.
  • Breakpoints, stepping, and stack traces through DAP on port 6006.
  • ClassDB and inheritance inspection, import/export operations, autoloads, signals, plugins, and version checks.
  • Optional searches and downloads for external CC0 assets when network and provider access are available.

Scene tools accept common vector forms such as coordinate objects or arrays. Explicitly tagged Godot values using a type field are recommended when cross-tool consistency matters.

Limitations and notes

The gopeak MCP server does not make every group available without conditions. Runtime and testing features may need a runtime addon or editor support; LSP and DAP require their corresponding Godot services; editor-plugin operations need plugin availability; and several scene, resource, import, animation, and project-setting operations are marked for audit or fixture verification. Asset-store operations depend on network and provider availability.

Godot version behavior also matters. For example, TileMap functionality must account for Godot 4.3 and later TileMapLayer behavior. If an MCP client caches tools aggressively, dynamically activated groups may not appear until the client reconnects or performs a fresh tools-list round-trip. The repository also identifies English as its canonical README source, with localized documents potentially lagging behind it.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Gopeak

gopeak is an MCP server that connects AI assistants to Godot 4.x projects. Its main tools let agents discover projects, inspect and edit scenes, scripts, and resources, run games, read debug output, and use optional LSP, DAP, runtime, testing, and asset workflows. Tool groups can be activated as needed.

Install it with `npx -y gopeak`, or run `npm install -g gopeak` and then start it with `gopeak`. Add the command to an MCP client configuration, provide `GODOT_PATH`, and ensure Godot 4.x and Node.js 18 or newer are installed.

Set `GOPEAK_TOOL_PROFILE` to `compact`, `full`, or `legacy`. Compact is the default and activates additional groups when needed; full exposes the complete legacy list; legacy retains the full-profile behavior for older configurations. `MCP_TOOL_PROFILE` works as a fallback alias.

Yes, Cursor is listed as an MCP-compatible client for gopeak. Configure the server command in Cursor using `npx` with the `gopeak` package, and provide the Godot path through the server environment configuration.

Activate the `dap` group with `tool.groups` for breakpoints, stepping, and stack traces. Godot DAP must be available on port 6006. For GDScript completions, hover, and symbols, activate `lsp` and provide Godot LSP on port 6005.

Related MCP servers

All in Gaming All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGopeak AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gopeak?style=directory)](https://allmcps.com/mcp/gopeak)
HTML Embed
<a href="https://allmcps.com/mcp/gopeak"><img src="https://allmcps.com/api/badge/gopeak?style=directory" alt="Gopeak on AllMCPs" /></a>