原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Beckett - MCP for Godot

注册名称io.github.beckettlab/beckett-godot-mcp

安装方法

能做什么

MCP server embedded in the Godot 4 editor; drive Godot with AI, zero sidecar.

作者提供的原文

  • 连接方式 –
  • 账号或密钥 无需密钥
  • 分类 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度21/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分33/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Beckett - MCP for Godot

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 Beckett - MCP for Godot

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 其他 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Beckett - MCP for Godot

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 Beckett - MCP for Godot

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 Beckett - MCP for Godot

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Beckett - MCP for Godot 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
–
最新版本i
1.17.0
分类i
其他
发布到注册中心i
2026年11月1日
代码最后更新i
2026年11月1日
作者
beckettlab
注册状态
活跃

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 beckettlab 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于19天前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/beckettlab-beckett-godot-mcp.svg)](https://mcp.popnx.com/en/servers/beckettlab-beckett-godot-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20868 个服务器的 98%
  • 发布到注册中心的时间比此分类中其他 20868 个服务器的 71% 更新
  • 基础检查结果等于或优于此分类中其他 20868 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Beckett - MCP for Godot 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于19天前,最新版本(1.17.0)于19天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万4天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92762个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582414个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
Beckett - MCP for Godot
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/34/44/44/41/44/4
许可证MITAGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Beckett — MCP for Godot

*Stop waiting for Godot.*

Beckett is a zero-sidecar Model Context Protocol (MCP) server embedded directly in the Godot 4 editor as a GDScript EditorPlugin. AI agents (Claude and others) drive the editor over HTTP — no Node/Python bridge, no second process, no cloud.

This repository is the free, MIT-licensed Lite edition: the complete inspect → author → run → SEE dev loop (56 tools), for **GDScript *and* C#**. The AI can now *watch your running game* on the free tier: screenshot it, read the live remote scene tree and node state, poll performance monitors, and tail the game's logs. The paid Full edition makes the AI the *playtester* (it drives input, clicks 2D/3D and UI, and asserts the results), plus a test runner, animation tools, scatter_nodes, background exports, project-wide analysis, and 46 knowledge packs. See What Full adds.

Lite: the AI sees your game. Full: the AI playtests it.

Demo

Why

Existing Godot MCP servers either shell out to the CLI (can't play the game, screenshot, or inspect runtime) or run a Node/Python sidecar that relays to a thin in-editor addon. This one makes the addon itself the MCP server, and exposes reflection-generic tools that work on *any* class via ClassDB — instead of hundreds of hand-coded per-domain wrappers (an anti-pattern: LLMs degrade past ~40 tools).

Highlights

  • Zero-sidecar — TCPServer HTTP/JSON-RPC server polled on the editor main thread. No marshalling, nothing extra to install beyond the addon.
  • The AI sees your game (free) — screenshot the running game, read the live remote scene tree (get_remote_tree / find_nodes / wait_for_node), read live node state (runtime_get_property / monitor_properties), poll get_performance_monitors, and tail game_logs with stack traces. The free tier can watch and diagnose the running game; Full closes the loop by driving input and asserting the result.
  • GDScript and C#, one addon, zero sidecar — the C#/.NET dev loop is free too: build_csharp runs a dotnet build compile-check that returns structured file:line:col + CS-code diagnostics (safe while the editor is open, no new dependency beyond the .NET SDK a C# project already needs), write_script is .cs-aware, and reflection surfaces your C# [GlobalClass] types just like GDScript class_name.
  • Reflection-first + discovery — find_classes / describe_class / find_methods make the whole engine surface searchable; describe_object / set_property / call_method then drive any Node / Resource / Object. Reaches TileMap, GPUParticles, AnimationTree, NavMesh, shaders… with no per-domain code.
  • GDScript dev-loop with validate-before-write — write_script / script_patch parse the code first and refuse to write what doesn't compile (closing the #1 AI-on-Godot failure: hallucinated GDScript). Godot's edge over UE: reload needs no compile step.
  • Undoable authoring — every scene/node mutation goes through EditorUndoRedoManager (atomic + undoable); batch_execute rolls a whole batch back on failure.
  • One-step install — enabling the plugin auto-starts the server and writes .mcp.json, so claude/Cursor connects with zero hand-editing (no Node.js to install — the competitor needs it just to try).
  • Security: localhost-only, with exact Host and Origin checks (anti DNS-rebind), a per-project token for new projects, file reads confined to the project, and read-only / allowlist / confirm-destructive gates; auto-start is opt-out (beckett/autostart=false). SECURITY.md says what is protected, what is not, and how to report a problem.
  • Run → see loop — play_scene → wait_until → logs_read → screenshot / get_remote_tree → fix: launch the game, tail its output and errors, then look at the running frame and live scene tree to diagnose. (Full closes the loop autonomously: the AI drives the game and asserts.) Plus MCP Resources + Prompts.
  • Dock panel — status, one-click Start/Stop, copy-client-config, and an AI-effort slider (1–4 in Lite; L4 = *See*) that caps how many tools are advertised: cheaper model context when you only need a slice. Applies live, no reconnect — the server pushes notifications/tools/list_changed over its SSE stream and list-changed-aware clients (Claude Code, Cursor, …) re-fetch on the spot.
  • Responsive even unfocused — while MCP traffic is active the server clamps the editor's low-processor sleep, so calls stay fast when you're focused on the terminal instead of the editor (the usual agent setup).
  • Spec-current MCP — protocol version negotiation, tool annotations (readOnlyHint/destructiveHint/openWorldHint) on every tool, and structuredContent (2025-06-18) alongside text results. An audit ring (audit://recent) records the last 200 tool calls — see everything the AI did.

Tools (56) · Resources (6) · Prompts (6)

Fewer tools, on purpose — that's the moat, not a limitation. Most Godot MCPs hand-code one tool per task (create_sprite, add_collision, make_timer…) — hundreds that *still* miss classes and flood the model's context (LLMs measurably degrade past ~40 tools). Beckett's are reflection-generic: describe_class / set_property / call_method drive *any* of Godot's 1000+ classes through ClassDB — TileMap, GPUParticles, AnimationTree, shaders, your own class_name or C# [GlobalClass] — with no per-domain code. Don't count tools, count coverage: a smaller, sharper toolset that reaches the *whole* engine beats a hundred narrow wrappers that don't.

The free Lite edition — the complete inspect → author → run → see loop, for GDScript and C#:

  • Reflection / discovery: get_godot_version, find_classes, describe_class, find_methods, describe_object, set_property, call_method, get_scene_tree
  • Scene authoring (undoable): create_node, delete_node, rename_node, reparent_node, duplicate_node, move_node, instance_scene, save_scene, open_scene
  • GDScript dev-loop: validate_script, write_script, script_patch, read_script, attach_script
  • C#/.NET dev-loop: build_csharp (a dotnet build compile-check returning structured file:line:col + CS-code diagnostics, safe while the editor is open, zero new dependency; write_script is .cs-aware and C# [GlobalClass] types show up in reflection)
  • Signals: connect_signal, disconnect_signal, list_signals
  • Resource assets: create_resource, set_resource
  • Files / project: read_file, write_file, list_dir, search_files, rescan_filesystem, get_project_setting, set_project_setting
  • Run loop: play_scene, stop_scene, get_play_state, wait_until, logs_read
  • Runtime observation (the AI sees your game): screenshot, ui_snapshot (every visible Control as structured state in one call), get_remote_tree, find_nodes, wait_for_node, runtime_get_property, monitor_properties, get_performance_monitors, game_logs
  • Render diagnosis: render_probe (why a 3D node is or is not on screen, as data: visibility chain, frustum, cull mask, material cull mode, triangle winding) and set_debug_draw (switch the running game's debug draw mode, then screenshot one render stage)
  • Project / authoring helpers: get_project_statistics, apply_template, batch_execute, doctor (one-call self-diagnosis: edition, effort cap, server and auth state, client configs, and what the tool list costs your context per tier), help (any tool's full argument catalogue, on demand)
  • MCP Resources: scene://tree, scene://selection, project://settings, assets://list, log://output, audit://recent
  • MCP Prompts: inspect_node, audit_scene, setup_2d_player, fix_script_errors, build_test_fix, make_game

What Full adds

The Full edition is the same core plus a premium layer that makes the AI the *playtester*: it sees the screen, presses the buttons, and verifies the result. 92 tools, 46 skill packs total:

  • The AI drives: simulate_input, UI clicks in 2D + 3D (click_button_by_text / click_control / click_node3d / click_world), scroll / drag, get_control_rect / find_ui_elements, live runtime_call / runtime_set_property, and record_input / replay_input.
  • The AI verifies: assert_node_state, assert_screen_text, assert_scene, compare_screenshots, plus the in-editor test runner (test_run).
  • Author + ship: animation_manage (keys / tracks / presets), scatter_nodes (Scene-Paint mass placement), background export_project + job_status, project-wide analysis (find_unused_resources, detect_circular_dependencies), and the Godot Asset Store / Library browser-installer (asset_lib_search / asset_lib_info / asset_lib_install).
  • 46 skill knowledge packs (list_skills / load_skill): gdscript, particles, animation, ui, physics, multiplayer, mobile, and more, so reflection reaches each domain with no per-domain tools.

Lite ships the game-side runtime (addons/beckett/runtime/mcp_runtime.gd, MIT source) that Full's drive tools use, and that runtime understands the drive commands. Lite's tools never send them and Lite's bridge refuses them, so Lite sees the running game without driving it. This is a product boundary, not a sandbox; SECURITY.md has the details.

Full is a one-time purchase ($15) with lifetime updates: https://beckettlabs.itch.io/beckett-godot-mcp

How it compares

Beckett is one of only a few *embedded* (zero-sidecar) servers in the field, and its free tier includes *seeing the running game*, as Native's does. The other players have real strengths (raw tool count, mindshare, breadth), so here's an honest side-by-side. (Competitor figures are their own published numbers; they ship far more hand-coded per-domain tools, which is a different design choice, not strictly "more capability": see Why.)

Beckett Lite (free, MIT)Beckett Full ($15)CLI shell-out (e.g. Coding-Solo, free)Sidecar (godot-mcp-pro, $15, Node 18+)Native (free, embedded, 4.6+ only)
Zero sidecar (no Node/Python)✅✅❌ (Node CLI shell-out)❌ (Node 18+ + TS server)✅ (embedded)
The AI sees the running game (screenshot, live tree, live state)✅ free✅⚠️ CLI debug output only✅ (paid)✅ (free)
The AI drives + asserts (playtest: input, clicks, asserts)❌✅❌✅ (input record/replay)⚠️ partial
Validate-before-write (refuses non-compiling GDScript)✅✅❌❌❌
C# + GDScript✅✅❌ (GDScript)❌ (GDScript)❌ (GDScript)

| Godot 4

只显示了开头部分;其余内容请在仓库中阅读