
AI Workbench MCP
io.github.hrishikesh-thakre由 GitHub 账号 hrishikesh-thakre 发布v0.6.0a0更新于 Nov 3, 2026
Goose-first MCP server for Workbench-owned acceptance evidence, validation gates, and analytics.
概览
本地 MCP 服务器,用于监督 AI 编码代理、采集运行证据、校验工作并生成 accept、needs_review 或 block 的 PR 门禁结论。
- 可以做什么
- 开启并配置运行:启动运行、选择策略包、选择模型。
- 记录代理执行过程并为该运行采集本地证据。
- 校验运行并写出校验报告,再执行质量门禁并写出修订决定。
- 分析多次运行并生成可直接用于 PR 的报告,结论为 accept、needs_review 或 block。
- 适用场景
- 当你希望为本地仓库中 AI 编码代理的工作留下可审计的验收记录时使用:证据采集、校验配置、质量门禁与 PR 报告,尤其适用于 Goose、Codex 或 OpenCode 工作流。
- 运行要求
- 以本地 Python 进程运行,从 PyPI 包 ai-workbench-mcp 安装,命令行名为 ai-workbench。需先注册项目目录并启动本地 supervisor;Codex 钩子需安装并信任一次。未声明任何账号、API 密钥或环境变量。
安装
在 SourceWeft 中
- 打开 控制台中的 AI Workbench MCP,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
AI Workbench
AI Workbench supervises AI coding agents, captures evidence, validates work, applies acceptance policy, and produces auditable PR-ready reports.
The PyPI package remains ai-workbench-mcp for this public alpha because the
ai-workbench package name is already occupied. The product and CLI are
AI Workbench:
Current source metadata targets unpublished ai-workbench-mcp==0.8.0a0.
This public alpha consolidates local supervision, evidence capture, validation,
acceptance policy, and PR reporting into one product surface.
Public Alpha Warning
The supervisor is the preferred automated evidence path, but daemon, Codex hook, and OpenCode adapter coverage are alpha mechanisms. AI Workbench checks evidence quality and acceptance readiness; it does not prove the work is absolutely correct. High-risk work still requires human review.
Architecture
- AI Workbench supervisor captures local evidence.
- AI Workbench validation writes
validation_report.json. - AI Workbench quality gate writes
revision_decision.json. - AI Workbench PR/report surfaces render
accept,needs_review, orblock.
Agent output is a proposal. Workbench accepts evidence.
MCP is the connection protocol. AI Workbench MCP is the tool server. Acceptance is decided by the selected validation profile and quality gate. The agent performs. Workbench accepts. MCP connects them.
Quick Start
Register a project once and start the local supervisor:
Run Codex, OpenCode, Goose, or another supported local workflow in the project. Then inspect the latest report:
Render PR-ready artifacts from a finalized run:
The canonical local run ledger is:
validation_report.json and revision_decision.json are the final acceptance
authority. Supporting supervisor reports are local evidence, not a substitute
for those Workbench artifacts.
Codex Hooks
Install project-local Codex hooks:
Restart Codex or start a new session, open /hooks, review the project hook,
and trust it once. Until a hook event is observed, supervisor status reports
Codex coverage as configured but unverified.
Goose MCP
AI Workbench still exposes the same MCP tool lifecycle. Register the server with Goose or another MCP host using:
The seven MCP tools remain:
PR Gate
Workbench PR acceptance consumes real Workbench run evidence:
Outcomes are exactly:
acceptneeds_reviewblock
Missing, unreadable, or scaffold-only evidence blocks. A green CI run, uploaded artifact, sticky PR comment, or model self-claim is not acceptance evidence.
Bootstrap Assets
To add starter configs, prompts, recipes, docs, and the GitHub PR-gate workflow to a repository:
The bootstrap keeps runs/ ignored.
Package Demo
For a package-only synthetic demo:
This shows accept, needs_review, and block PR-gate outcomes with fixture
evidence. It is not a real target-repository acceptance run.
Development
Do not commit runs/. Committed sample evidence must be sanitized and live
under examples/.
Docs
- Supervisor docs
- Evidence folder contract
- Transcript schema
- Workspace hygiene
- Confidence rules
- How acceptance works
- Contract baseline
- Package demo walkthrough
- Codex setup
- Codex live-test handoff
- Codex acceptance walkthrough
- Acceptance analytics
- Evidence dashboard
- Event ledger
- Golden-case harness
- Model registry
- Dogfooding guide
- Goose demo walkthrough - recording-ready 3-5 minute public demo runbook
- Policy packs
- PR gate
- Launch issues
- Repository topics
- Create launch issues
- Publishing guide
- Gemini fixture proof
- Codex fixture proof
Recipes:
- Engineering acceptance
- MCP tool smoke
- Docs-only acceptance
- Python package maintenance
- Test-fix acceptance
Sample evidence:
- Accepted tiny Python fix
- Accepted Codex tiny Python fix
- Accepted docs-only smoke
- Needs-review test fix
License
Apache-2.0. See LICENSE. MIT-origin attribution for the consolidated Prove It code is retained in NOTICE.
来源:README.md,提交 c86ff8f
工具
0版本历史
1- v0.6.0a0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分