
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 分