AI Workbench MCP server
io.github.hrishikesh-thakre/ai-workbench-mcp·v0.6.0a0Goose-first MCP server for Workbench-owned acceptance evidence, validation gates, and analytics.
0 stars32 downloads/wk
Reviews
Write oneNobody has reviewed AI Workbench MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AI Workbench MCP tools (7, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
workbench_analyze_runsAnalyze local Workbench run ledgers and write report artifacts.
workbench_open_runwrite actionCreate a Workbench run folder and initial evidence artifacts.
workbench_quality_gatewrite actionRun the Workbench quality gate for a run directory.
workbench_record_executionCapture Goose/model response text into Workbench evidence artifacts.
workbench_select_modelSelect a Workbench model tier and write model_selection.json.
workbench_select_policy_packRecommend an advisory Workbench policy pack from task metadata.
workbench_validate_runwrite actionRun deterministic Workbench validation over a run directory.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan37 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 92 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumsubprocess with shell=True
exec.shell-trueai_workbench_mcp-0.6.0a0/src/ai_workbench_mcp/tools/validate_run.py: …, cwd=cwd_path, shell=True, stdin=subprocess.DEVNULL, …
How AI Workbench MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 74/100
- higher than 40% of 48,255 servers
- Tools
- 7
- the typical server has 7
- Tools that change things
- 43%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 32
- more than 20% of 12,191 servers with a package
What its tools let an agent do: 4 read · 3 change
Install AI Workbench MCP in Claude Code, Cursor or VS Code
claude mcp add ai-workbench-mcp -- uvx ai-workbench-mcp
What the publisher says
From the AI Workbench MCP repository's README, as published. We do not edit it. Read it on GitHub
AI Workbench
<!-- mcp-name: io.github.hrishikesh-thakre/ai-workbench-mcp -->
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:
pip install ai-workbench-mcp
ai-workbench --helpCurrent 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, 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.
Quick Start
Register a project once and start the local supervisor:
pip install ai-workbench-mcp
ai-workbench supervisor setup --project-dir . --task-type code_change
ai-workbench supervisor startRun Codex, OpenCode, Goose, or another supported local workflow in the project. Then inspect the latest report:
ai-workbench supervisor status
ai-workbench reports show latest --project-dir .Render PR-ready artifacts from a finalized run:
ai-workbench pr-gate --run-dir runs/<run_id>The canonical local run ledger is:
runs/<run_id>/
task_metadata.json
final_prompt.md
model_selection.json
model_output.md
validation_report.json
revision_decision.json
run_log.jsonl
metadata.json
transcript.jsonl
commands.jsonl
workspace/
validation/
artifacts/validationreport.json and revisiondecision.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:
ai-workbench setup codex --project-dir . --task-type code_changeRestart 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:
ai-workbench mcp serveThe seven MCP tools remain:
workbench_open_run
workbench_select_policy_pack
workbench_select_model
workbench_record_execution
workbench_validate_run
workbench_quality_gate
workbench_analyze_runsPR Gate
Workbench PR acceptance consumes real Workbench run evidence:
ai-workbench pr-gate \
--run-dir runs/<run_id> \
--out runs/pr_gate/pr_comment.md \
--json-out runs/pr_gate/pr_decision.jsonOutcomes are exactly:
- accept
- needs_review
- block
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:
ai-workbench bootstrap --target .The bootstrap keeps runs/ ignored.
Package Demo
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
AI Workbench MCP: common questions
- Is AI Workbench MCP server safe?
- Mostly: it is graded B (74/100). Read the AI Workbench MCP safety report
- How do I install AI Workbench MCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does AI Workbench MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is AI Workbench MCP maintained?
- The last commit was 130 days ago (2026-06-27). The latest release is v0.6.0a0.
- How does AI Workbench MCP compare with other MCP servers?
- safety score 74/100 (higher than 40% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 43% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.