The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the AI Workbench MCP listing page.
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.
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.
validation_report.json.revision_decision.json.accept, needs_review, or block.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.
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.
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.
AI Workbench still exposes the same MCP tool lifecycle. Register the server with Goose or another MCP host using:
The seven MCP tools remain:
Workbench PR acceptance consumes real Workbench run evidence:
Outcomes are exactly:
acceptneeds_reviewblockMissing, unreadable, or scaffold-only evidence blocks. A green CI run, uploaded artifact, sticky PR comment, or model self-claim is not acceptance evidence.
To add starter configs, prompts, recipes, docs, and the GitHub PR-gate workflow to a repository:
The bootstrap keeps runs/ ignored.
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.
Do not commit runs/. Committed sample evidence must be sanitized and live
under examples/.
Recipes:
Sample evidence:
Apache-2.0. See LICENSE. MIT-origin attribution for the consolidated Prove It code is retained in NOTICE.