MCP

Beckett: enable the plugin in Godot 4, inspect first, then change the game

For inspecting a game from Claude or Cursor inside the Godot 4 editor without an extra process. Enabling the plugin writes .mcp.json automatically. Start with inspect; author/run have a confirm gate.

Official source · Beckett

Install

Enable the Beckett EditorPlugin (writes .mcp.json)

Who it's for

You make GDScript or C# games in the Godot 4 editor and want Claude or Cursor to inspect, author, run, and see the scene directly — without hanging a Node or Python bridge, a second process, or the cloud. Beckett is a GDScript EditorPlugin embedded in the editor, zero sidecar.

Free MIT Lite covers the full inspect → author → run → SEE loop, 55 tools in total. This page does not name those 55 tools, so do not invent scene-tree or script tool names.

Official repo on its own line:

https://github.com/beckettlab/beckett-godot-mcp

First try in 3 minutes

Use the official one-step install: enable the plugin in Godot 4. After enable, the service starts by itself and writes .mcp.json so claude or Cursor can connect without hand-editing config. Node.js is not required.

Prerequisite: you already have the Godot 4 editor and can open a project that contains this addon. Nothing else to install besides the addon. At runtime a TCPServer HTTP/JSON-RPC polls on the editor main thread.

Where to configure: the Godot plugin toggle, and the auto-generated .mcp.json in the project. Do not hand-write a server config that fights the auto file. If you do not want autostart, official text gives an opt-out: beckett/autostart=false.

Low-risk first step: inspect first — only observe the project, do not author or run. Success signal: after the plugin is enabled the service is up, .mcp.json appears, and Claude or Cursor can connect. This page has no concrete inspect tool name; do not invent one.

Safety boundary: listen on localhost only, with Origin checks (against DNS-rebind), an optional bearer token, and read-only / allowlist / confirm-destructive gates. Do not read localhost as offline or as no local reads; it still opens HTTP on this machine and reads/writes the project in the editor. readOnlyHint is not zero risk.

Before you change a scene or run the game, confirm that destructive actions need confirmation. author and run change the project or start the game; official text gives no undo command.

Use cases

Case 1: inspect the current project first. Enable the plugin, let the client connect via .mcp.json, and use inspect only. Which of the 55 tools belong to inspect is not named. GDScript and C# are both in Lite.

Case 2: before authoring or running, open the confirm gate. The official loop is inspect → author → run → SEE. author changes the project; run plays the game in the editor. There are confirm-destructive and allowlist. Without a tool name, do not call a write. Official text does not say how to generate the optional bearer token.

Limits

Zero sidecar is not the same as no local HTTP. No cloud and no second process, but it still binds localhost. It writes .mcp.json automatically; beckett/autostart=false turns autostart off. The 55 tools are unnamed. Lite is the free MIT edition. Official text does not write a port number, a Godot minor version, or how to delete .mcp.json after uninstall.