Gopeak MCP Server

Gopeak MCP server exists for a simple reason — assistants are far more useful when they can act on Gopeak directly instead of describing what you should do. GoPeak — The most comprehensive MCP server for Godot Engine. 95+ tools, LSP, DAP, screenshots.

What you get

It is designed for trusted Godot 4 workflows: small default tool surface, setup-gated advanced capabilities, and explicit compatibility rules for older/legacy tool names.

What the assistant can call

Once Gopeak is connected, these are the calls the assistant has available:

• Requirements — The Requirements tool exposed by this server

Configuration and credentials

You will need 3 environment variables: GODOT_PATH, GOPEAK_TOOL_PROFILE, GOPEAK_BRIDGE_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Godot 4.x - Bun 1.3.3+ - MCP-compatible client such as Claude Desktop, Cursor, Cline, or OpenCode

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Gopeak's toolset — Requirements — is a fair guide to whether it matches your workflow. It is maintained by HaD0Yun; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the gopeak mcp server does with a few real requests.