Spec Driven Development
作者：formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
在你的电脑上运行★ 440MIT14个月前更新
安装
Weapon Lab
概览
作者提供的说明（英文原文）
Find and fix first-person weapon bugs behind a gate: your game's probe measures, the Gate judges
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
- 使用情况i尚未统计★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 其他
安装
选择你使用的 AI 应用，然后复制设置。
安装之前
- 基础检查：1 项中通过 1 项
- 在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
- 需要你自己填写：
WEAPONLAB_PROJECT,WEAPONLAB_BLENDER
你需要
- PyPI已安装 Python 的 uv（用于 uvx 命令）
你用的是哪个应用？
在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"weaponlab": {
"command": "uvx",
"args": [
"weaponlab-mcp"
],
"env": {
"WEAPONLAB_PROJECT": "your-value",
"WEAPONLAB_BLENDER": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add weaponlab --env WEAPONLAB_PROJECT=your-value --env WEAPONLAB_BLENDER=your-value -- uvx weaponlab-mcp运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json
{
"mcpServers": {
"weaponlab": {
"command": "uvx",
"args": [
"weaponlab-mcp"
],
"env": {
"WEAPONLAB_PROJECT": "your-value",
"WEAPONLAB_BLENDER": "your-value"
}
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"weaponlab": {
"type": "stdio",
"command": "uvx",
"args": [
"weaponlab-mcp"
],
"env": {
"WEAPONLAB_PROJECT": "your-value",
"WEAPONLAB_BLENDER": "your-value"
}
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上，无需账户。
需要你填写的值
WEAPONLAB_PROJECTenvThe project folder holding weaponlab.json; the current folder if not setWEAPONLAB_BLENDERenvBlender's executable for Motion Lab, if it is not on the PATH or in the usual install folder
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。
它能做什么
它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 hpdkhoa 验证，该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表
与“其他”中的其他服务器比较i
- 星标数多于此分类中其他 32537 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 32537 个服务器的 62% 更新
- 基础检查结果等于或优于此分类中其他 32537 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。
常见问题
Weapon Lab 安全吗？
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。
它需要哪些密钥或代码？
注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端？
它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。
它还在维护吗？
GitHub 仓库最后更新于–，最新版本（0.1.0）于23天前进入注册中心。
哪些应用可以使用它？
支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
有什么可以替代它？
同一分类中有：Spec Driven Development, Remote Desktop Commander, TF Rooms
替代选择
同一分类中其他作者的服务器，按星标数排序。
如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Remote Desktop Commander
作者：desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
在云端运行★ 211昨天更新
安装
TF Rooms
作者：tfrooms.com
Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.
在云端运行今天更新
安装
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Weapon Lab
First-person weapon bugs fixed once per kind, then for every weapon, behind a gate.
An MCP server that finds and fixes first-person weapon bugs behind a gate: hands off the gun, a magazine crooked in its well, a blade held wrong, arms covering the screen.
Each bug becomes a case: a metric, a weapon, an action and a pass rule. Your game's own probe measures the weapons. The Gate passes a change only when its target cases pass and nothing else got worse. Fix each kind of bug once, then check every weapon with it.
Weapon Lab never runs your game itself. You write a small probe for your engine that follows the probe contract: a job file in, a rows file out. Everything else works on what the probe writes back.
What it does
| Group | Tools | What for |
|---|---|---|
| Gate | gate_run, gate_verdict, gate_propose, gate_approve, gate_set_baseline, gate_cases, ... | Keeps the bugs as cases, measures, compares against a baseline, judges a change, records a person's approval. |
| Probe | probe_run, probe_plan, probe_status | Starts your game's probe. Tries a fix before it is written: tuned fields, staged assets, screenshots, parts dumps. |
| Rig Lab | rig_pieces, rig_facts, rig_align, rig_part_line, rig_fist | Reads the posed weapon from a parts dump: its pieces, real-world facts (the magazine behind the barrel), a magazine's line into its well, a hilt in the fist. |
| Motion Lab | motion_roll, motion_roll_profile, motion_roll_set, motion_track, motion_render | Rebuilds clips in Blender: turns a hand about its forearm inside the forearm's range, puts a sliding part back on its axis. |
| Specs | spec_list, spec_read, spec_validate, spec_write | One file a weapon: marks (grip, support), anchors (pieces to find), facts, limits. |
| Contract | contract_check | Checks a probe's job, rows or parts dump. |
| Gun Kit | gunkit_inspect, gunkit_draft, gunkit_from_modellab, gunkit_proxy, gunkit_rig, gunkit_build, gunkit_verify, gunkit_export, gunkit_cases, gunkit_actions, gunkit_action | Takes any gun model to the game: rigs it for one of 18 actions, makes its own clips and the hand clips on one shared pair of arms, checks them, stages the files. See docs/GUNKIT.md. |
| Blueprint Lab | blueprint_source_add, blueprint_scan, blueprint_specs, blueprint_figure_add, blueprint_calibrate, blueprint_trace, blueprint_part, blueprint_check, blueprint_build, blueprint_to_gunkit, ... | Makes a real gun's visual copy from its public sources (manuals, patents, photos): facts from the data tables, outlines traced from scaled figures, a blueprint with the source of every number, the model built in Blender. See docs/BLUEPRINT.md. |
Try it on the demo
The demo is a toy game with two planted bugs and a probe in about 150 lines. It needs no engine.
pip install -e .cd examples/demo weaponlab gate run probe,rig
(python -m weaponlab works the same when pip's scripts folder is not on your PATH.)
The rifle's left hand misses its handguard by 3.75 cm. The knife's hilt lies 90 degrees across the fist. tests/test_demo.py walks the whole loop: measure, find the fix, try it by tune, judge it.
Use it in your game
weaponlab initin your project. It writesweaponlab.jsonand empty data files.- Write your probe from the contract, starting from
examples/demo/probe/demo_probe.py. Set its command inweaponlab.json. - List your weapons in
weaponlab/data/weapons.jsonand their actions inactions.json. - Add a case for each bug you know. Measure everything once and set the baseline.
- Fix through the loop: try by tune or staging, look at the screenshots, propose, approve, import.
Check your probe on its own with weaponlab contract job|rows|parts .
Add it to an MCP client
{"mcpServers": {"weaponlab": {"command": "weaponlab-mcp", "env": {"WEAPONLAB_PROJECT": "C:/path/to/your/game"}}}}| Setting | Meaning |
|---|---|
WEAPONLAB_PROJECT | The project folder with weaponlab.json. The current folder by default. |
WEAPONLAB_BLENDER | Blender, for Motion Lab. Found on the PATH or in the usual install folders otherwise. |
Requirements
- Python 3.10 or later.
- Blender 4.4 or later for Motion Lab and renders. Nothing else needs it.
- Hand bones named as Unreal's mannequin names them (
hand_r,index_01_r,lowerarm_r) for the fist measure and the forearm roll.
Where it came from
Weapon Lab is the general part of the tools built for ToangTown, an Unreal 5.8 game with 46 weapons. Its first probe is ToangTown's. The contract's lessons come from that probe. Pose Lab (poselab-mcp) answers the body's side: clipping, the view, a grip solver. The Gate can use it as a provider.
License
MIT