Ziva Sh

MCP开发工具

提供方 未标注

开发工具 未标注 未标注 官方维护 ClaudeCursorVS CodeGemini CLI

专有的 Godot 编辑器 AI 代理,配备本地 MCP 服务器,可让 Cursor 和 Claude Code 检查场景树、读取 Godot 错误、截取编辑器屏幕截图并运行场景。

一句话选型结论

按资料字段整理

Ziva Sh 属于开发工具类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 官方维护 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

开发

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Ziva Sh当前 未标注 未标注 未标注 无 2026-11-20
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方官方维护核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

6.3 KB
来自项目仓库与上游目录的原文,未做删改

Star Catcher: a Ziva sample for Godot 4

A small, original Godot 4 game used to show what Ziva, an AI assistant inside the Godot editor, does with one ordinary request. Move the square with the arrow keys and collect stars. Each star is meant to add one point to the score label.

The project on main has one deliberate bug, the kind you get after moving a node into its own scene: main.gd looks up the score label with %ScoreLabel, but the label now lives in hud.tscn, so its unique name only resolves inside that scene. The game starts with a Node not found error, collecting a star then throws a null-instance error, and the score label never changes.

The recording

recording/ziva-star-catcher-run.mp4 (85 s, silent) is one unedited, real-time screen recording of the Godot editor with the Ziva panel on the left. Captions under the frame say what is happening; recording/captions.srt has the same text. recording/ziva-star-catcher-run-raw.mp4 is the same take without captions. It is also on YouTube as a square Short with the same captions: https://www.youtube.com/shorts/l7fjl7f2sEg

What you see, in order:

  1. One prompt is sent to Ziva.
  2. Ziva reads the scene tree and the project's three scripts and three scenes.
  3. Ziva edits star.gd (spin) and main.tscn (two new stars). The 2D view updates to five stars.
  4. Ziva runs the game in the editor and holds the ui_right input action (run_scene injects the action; no physical key is pressed). The player touches a star, the star disappears, and the score stays at 0.
  5. The Debugger shows the error: Node not found: "%ScoreLabel" (relative to "/root/Main"), then Invalid assignment of property or key 'text' ... on a base object of type 'null instance' at main.gd:15.
  6. Ziva reads that error from the run, explains it, and changes the lookup in main.gd to $HUD/ScoreLabel.
  7. Ziva runs the game again, holding ui_right for a shorter time. The score reads Score: 1. Ziva then reports what it changed and what it saw in the run screenshots.

The prompt was entered by Ziva's test harness, which types it into the Ziva composer and presses send. Nothing else touched the editor, the files or the Ziva panel until the recording ended.

The exact prompt```

Add two more stars to the level and make the stars spin slowly. Then play the game, grab a star with the arrow keys and check that the score goes up.


That was the only message. The prompt does not mention the bug.

## What Ziva changed

Branch `ziva-run-2026-11-04` has Ziva's changes from the recorded run as one commit, unmodified:```diff
--- a/main.gd
+++ b/main.gd
-@onready var score_label: Label = %ScoreLabel
+@onready var score_label: Label = $HUD/ScoreLabel
--- a/main.tscn
+++ b/main.tscn
+[node name="Star4" parent="Stars" instance=ExtResource("3")]
+position = Vector2(300, 300)
+
+[node name="Star5" parent="Stars" instance=ExtResource("3")]
+position = Vector2(620, 180)
--- a/star.gd
+++ b/star.gd
+const SPIN_SPEED := 1.2  # radians per second
+
+
+func _process(delta: float) -> void:
+   rotation += SPIN_SPEED * delta

Ziva's tool calls, in order: get_scene_tree, glob (twice), read (six files), edit_file on star.gd and main.tscn, get_scene_tree, run_scene holding ui_right from 300 ms to 1500 ms, edit_file on main.gd, clear_output_logs, run_scene holding ui_right from 300 ms to 900 ms. Each run_scene returns a screenshot of the running game plus the console output and runtime errors from that run. The panel's +/- line counts include the replaced lines of each search-and-replace edit, so they differ from this diff.

Play the fixed version in your browser

The fixed version from branch ziva-run-2026-11-04 is playable at https://play.ziva.sh/timely-hallway/. It was published on 5 November 2026 with Ziva's Share Web build (chat header ⋮ menu), which ran Godot 4.7.2's single-threaded web export, uploaded the 9 compressed files (13.5 MB) and returned that link. Use the arrow keys. How it works, and other ways to host a Godot web build: How to export a Godot game to the web and share a playable link.

Reproduce it

  1. Install Godot 4.7 and the Ziva plugin (installation guide), and sign in.
  2. Clone this repository and open it in Godot. Keep main checked out: it has the bug.
  3. Open main.tscn and send the prompt above in a new Ziva chat. To match the recording, turn on Auto-approve all actions in Ziva's settings under Agent; otherwise approve each edit and run by hand.
  4. Compare your result with the diff above. Model output varies between runs: star positions and wording will differ, and Ziva may spot the bug while reading main.gd before it runs the game.

To check the bug without Ziva, press Play (F5) and walk right into the first star: the Debugger shows the same two errors.

How it was recorded

  • Date: 4 November 2026. Godot 4.7.2 on Linux. Model: Ziva Smart, Ziva's default model.
  • Before recording, auto-approve was turned on, the editor setting Run > Bottom Panel > Action on Play was set to Open Debugger, and the bottom panel was enlarged so the Debugger is readable.
  • Ziva ran as a development build from Ziva's source (that is why the panel tab says "ZivaDev" and shows a per-turn cost), signed in to a local test account rather than a customer account.
  • The editor ran in a virtual X display (Xvfb, 1440x900) and the screen was recorded with ffmpeg at 30 fps. The take is one continuous file from before the prompt to after Ziva's reply; nothing is cut, sped up or reordered. Captions sit in a strip added below the frame.
  • The first four Debugger lines (_create_xic, set_use_vsync, init_output_device, All audio drivers failed) come from the virtual display having no input method, vsync or audio device. They are not from this project.
  • Four takes were run on 4 November. In the three that used this exact bug, Ziva found it by running the game and reading the error. An earlier version of the sample used $HUD/Score on a label inside main.tscn; Ziva noticed that one while reading the script and fixed it before running, so the sample moved the label into its own scene. The published take is the last of the three; the other two are not published because the editor's Debugger panel was hidden or too small to read during the run.

License

MIT, see LICENSE. The game itself (code, scenes and shapes) is original and contains no third-party assets.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Ziva Sh 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Ziva Sh 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Ziva Sh 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Ziva Sh 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Ziva Sh 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Gemini CLI、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Ziva Sh 能提供哪些能力?

资料显示能力标签包括 开发。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。