Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
RLHF feedback loop for AI agents. Capture signals, promote memories, block mistakes, export DPO.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"rlhf-feedback-loop": {
"command": "npx",
"args": [
"-y",
"rlhf-feedback-loop"
]
}
}
}在终端中运行这条命令
claude mcp add rlhf-feedback-loop -- npx -y rlhf-feedback-loop粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"rlhf-feedback-loop": {
"command": "npx",
"args": [
"-y",
"rlhf-feedback-loop"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"rlhf-feedback-loop": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"rlhf-feedback-loop"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 IgorGanapolsky 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.6.13)于8个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, arr-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One server, 40 tools, the whole media stack: *arrs, Jellyfin, Plex, Seerr, Cleanuparr, downloaders
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
ThumbGate is the self-improving pre-action firewall for AI coding agents
AI coding agents repeat mistakes — and one wrong tool call can wipe a directory, leak a key, or push broken code.
ThumbGate is the local-first Pre-Action Checks engine for AI coding agents. It runs in the PreToolUse hook to evaluate the proposed tool call before execution — so costly mistakes can be caught before they happen.
ThumbGate GitHub star growth is measured with GitHub's privacy-safe GET /repos/{owner}/{repo}/stargazers/history endpoint (weekly counts, no stargazer identities). Run npm run stars:history -- --fixture tests/fixtures/github-star-history.json --json for the local proof. Stars are not npm installs and not revenue. The live GitHub Marketplace Action is ThumbGate Agent Governance (uses: IgorGanapolsky/ThumbGate@v1).
Usage over star count. Evaluate ThumbGate from the install path and live usage badges above (npx thumbgate init, Marketplace uses:, npm weekly downloads, GitHub clones), not from whether the repo has twenty stars or twenty thousand. No pitch deck is required. We do not farm GitHub profile badges (no YOLO-merge of protected main, no 5-minute Issue close theater, no fake Co-authored-by). Galaxy Brain needs real accepted answers in Discussions Q&A. npm run github:achievements -- --fixture tests/fixtures/github-achievements.json --json inventories what is already earned vs what we refuse to farm.
ThumbGate is for operators whose AI coding agents can leak a secret or destroy a checkout before a human sees the tool call (Claude Code, Cursor, Codex, Gemini CLI, MCP). Discovery should reach those operators — not a star campaign.
ThumbGate is not a GitHub star package, not fake engagement, and not a substitute for npm installs or merged PRs. Real engagement is npx thumbgate init and a PreToolUse hook that actually fires.
Lightweight visuals for how agents fail without a pre-action gate:
| Meme | Meaning |
|---|---|
| Unchecked tool calls ship destructive commands. | |
| A prompt is advice; a PreToolUse hook is enforcement. |
It hard-blocks detected secret leaks and two direct self-disable command classes by default — commands that terminate the ThumbGate gate process or enable its bypass environment override. Other high-risk classes (rm -rf, force-push, fetch-and-run, direct guardrail edits) warn and log by default. Set THUMBGATE_STRICT_ENFORCEMENT=1 for strict enforcement (warnings become hard denies).
| Verdict | Default behavior |
|---|---|
| ⛔ Hard-block | Detected secret leaks; process-kill/environment-override self-disable |
| 👎 Warn + log | rm -rf, git push --force, fetch-and-run, direct guardrail edits — warn by default |
| 👍 Allow | Everything else |
Accepted feedback is stored as local lessons. Repeated concrete failures can become prevention rules that promote from warnings to blocking gates. The firewall improves from operations without retraining the model. Prompt evaluation (npx thumbgate eval) turns accepted feedback into reusable eval cases and local proof reports.
Honest disclaimer: ThumbGate does not update model weights. It intercepts tool calls at runtime. Local-first — no cloud required for the enforcement path.
Works with Claude Code, Cursor, Codex, Gemini CLI, Amp, Cline, OpenCode, and other MCP agents.
Agent tries: rm -rf tests/
ThumbGate: 👎 WARN + LOG — "Never delete test directories" Pattern matched: rm.*-rf.*tests Source: your thumbs-down from last Tuesday Strict mode: ⛔ DENY before tool execution
Agentic development is becoming a loop: Guide → Generate → Verify → Solve. ThumbGate is the pre-action gate / pre-action boundary between generated intent and executed action.
Want a phased walkthrough with a verify step at every stage? Follow the Progressive Setup Guide.
Progressive wiring — prove the pipe before you turn matching on. Empty dashboard is success.
npx thumbgate init # Phase 1: hooks only
npx thumbgate doctor # verify: exits 0 only when PreToolUse hook is wired (hidden metric = hook install, not gate count) npx thumbgate dashboard --open # Phase 2: open local HTML; empty stats are OK npx thumbgate capture --feedback=down --context="Never run DROP on production tables" --what-went-wrong="agent proposed DROP" --what-to-change="require review for DROP"
Later DROP attempts in the same scope surface the check:
⚠️ Check fired: "Never run DROP on production tables"
Pattern: DROP.*production Verdict: 👎 WARN + LOG (⛔ BLOCK when THUMBGATE_STRICT_ENFORCEMENT=1)
Numbered configs: config/progressive/. Guide: progressive wiring.
Directories and clients that install ThumbGate as an MCP server must start stdio MCP, not the HTTP API:
npx -y thumbgate serve
npx -y thumbgate mcpnpm start for MCP — that launches the hosted HTTP API (src/api/server.js), not the agent-facing stdio server.▶ 90-second demo · GIF walkthrough
| Agent | Command | Enforcement |
|---|---|---|
| Claude Code | npx thumbgate init --agent claude-code | 🛡️ Hard — PreToolUse |
| Codex | npx thumbgate init --agent codex | 🛡️ Hard — pre_tool_use |
| Gemini CLI | npx thumbgate init --agent gemini | 🛡️ Hard — PreToolUse |
| ForgeCode | npx thumbgate init --agent forge | 🛡️ Hard — pre_tool_use |
| Cursor | npx thumbgate init --agent cursor | 💬 Advisory — MCP gate_check |
| Cline | npx thumbgate init --agent cline | 💬 Advisory — MCP + .clinerules |
| OpenCode | npx thumbgate init --agent opencode | 💬 Advisory — MCP gate_check |
| Any MCP agent | npx thumbgate serve | 💬 Advisory — MCP gate_check |
| Amp | npx thumbgate init --agent amp | 📝 Feedback capture |
| GitHub Actions | uses: IgorGanapolsky/ThumbGate@v1 | 🩺 Marketplace Action — doctor / AI inventory in CI |
Per-agent guides: Claude/Codex bridge · Codex profile · Cursor · MCP setup
| Scope | Command | Settings | Lessons | Best for |
|---|---|---|---|---|
| Machine-wide (default) | npx thumbgate init | ~/.claude/settings.json | ~/.claude/memory/feedback/ | Solo operators — same machine-local feedback store across repos |
| Per-project | npx thumbgate init --project | /.claude/settings.json | /.claude/memory/feedback/ | Client / compliance — separate dashboard / isolated lessons per repo |
Both scopes write mcpServers.thumbgate plus PreToolUse / UserPromptSubmit / PostToolUse / SessionStart hooks. Machine-wide is the right default for most developers. Cross-repo blocking is not automatic: a lesson learned in one project only applies elsewhere when you share the store (machine-wide) or export/import lessons.
MCP tools (surface): gate_check (read/evaluate proposed tool call), feedback capture + session tools (write), dashboard/stats (read). Destructive agent actions stay blocked/warned by PreToolUse — ThumbGate does not execute user shell commands for you.
Spec-driven agent frameworks like GSD (get-shit-done) and GitHub Spec Kit plan and generate work. ThumbGate is the guardrail layer for spec-driven agents: it sits *after* the plan, on the boundary between a generated tool call and its execution — alongside GSD / Spec-Kit, not instead of them.
npx thumbgate init installs these into your agent palette:
| Command | What it does |
|---|---|
/thumbgate-dashboard | Open local project dashboard |
/thumbgate-guard | Turn last mistake into a hard prevention rule |
/thumbgate-rules | List active rules & lessons |
/thumbgate-blocked | Gate stats + enforcement matrix |
/thumbgate-protect | Branch governance + scoped approval |
/thumbgate-doctor | Health-check hooks, MCP, readiness |
Free tier: 2 feedback captures/day (10 total) and up to 3 active auto-promoted prevention rules. Pro ($19/mo or $149/yr) is the individual tier for unlimited rules, history-aware lessons, linked feedback session flow, personal dashboard, and DPO export. Enterprise is custom and scoped after intake; hosted team lesson sync and a hosted org dashboard are not general availability.
| Free | Pro ($19/mo or $149/yr) | Enterprise | |
|---|---|---|---|
| Local CLI + PreToolUse | ✅ | ✅ | Scoped after intake |
| Feedback captures | 2 feedback captures/day (10 total) | Unlimited | S
只显示了开头部分;其余内容请在仓库中阅读