Back to Directory/Analytics & BI

AI Workbench MCP

Goose-first MCP server for Workbench-owned acceptance evidence, validation gates, and analytics.

Analytics & BIPythonv0.6.0a0

AI Workbench

License

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 --help

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, 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 start

Run 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/

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:

ai-workbench setup codex --project-dir . --task-type code_change

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:

ai-workbench mcp serve

The 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_runs

PR 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.json

Outcomes 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

For a package-only synthetic demo:

ai-workbench demo --target ./workbench-first-run

This shows accept, needs_review, and block PR-gate outcomes with fixture evidence. It is not a real target-repository acceptance run.

Development

python -m pip install -e ".[dev,publish]"
python -m pytest -q -p no:cacheprovider
python -m ruff check . --no-cache
python -m mypy --no-sqlite-cache --no-incremental
ai-workbench demo --target runs/package_demo_smoke
ai-workbench validate --project ai_workbench_mcp --profile scaffold --run-dir runs/scaffold-smoke

Do not commit runs/. Committed sample evidence must be sanitized and live under examples/.

Docs

Recipes:

Sample evidence:

License

Apache-2.0. See LICENSE. MIT-origin attribution for the consolidated Prove It code is retained in NOTICE.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
uvx ai-workbench-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-hrishikesh-thakre-ai-workbench-mcp": {
      "command": "uvx",
      "args": [
        "ai-workbench-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

ai-workbench-mcppypi

Compatible MCP Clients

AI Workbench MCP works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More