The scoring tool your Claude agent calls before it recommends an AI deployment. It checks the business case, operating-model readiness, change enablement and governance exposure, then returns Accelerate, Fix, or Stop with a modelled EUR value.
Start with an AI proposal in plain English. The engine resolves the decision inputs, discloses estimated pillars and asks for missing context.
GR ≥ 70 or FR ≤ 20 returns Stop. SA, FR and CE ≥ 60 with GR ≤ 40 clear the pillar test for Accelerate. Accelerate also requires evidence that workflows, roles, decision rights and measures are ready. Missing or partial evidence, or a stated gap, holds the verdict at Fix.
Wire the gate into CI. Initiatives that can't survive a board review fail the build, before the budget is committed.
Choose a hosted connector or a local MCP client. Both expose the same thirteen tools.
In Settings, open Connectors, choose Add custom connector, and paste:
https://mcp.aibvf.com/api/mcp
Use this configuration in your MCP client, then quit and restart it:
{
"mcpServers": {
"aibvf": { "command": "npx", "args": ["-y", "aibvf-mcp"] }
}
}
Windows needs cmd /c. Open the client setup and troubleshooting guide for platform instructions.
Assess this AI initiative using AI BVF: we're a EUR 2.4bn manufacturer, planning a GenAI predictive maintenance rollout in our EU plants, we're a traditional hierarchy, strong sponsor, modest change budget.
The agent calls assess_ai_initiative and asks for unresolved decision inputs before returning a verdict. Estimated pillars are disclosed. For a Fix or Stop, ask for recommend_improvements, supply evidence and rerun.