Using Riven

MCP server

Riven can run as a Model Context Protocol server so other tools and agents can use the same graph-backed contract workflow that GitLab CI uses.

Build and run

bash

npm install
npm run build
npm run mcp

Add it to Claude Code

From a local checkout:

bash

claude mcp add riven -- node /path/to/blast-radius-governor/dist/mcp.js

Or use the installed binary:

bash

claude mcp add riven -- blast-radius-governor-mcp

Config shape

json

{
  "mcpServers": {
    "riven": {
      "command": "node",
      "args": ["/path/to/blast-radius-governor/dist/mcp.js"]
    }
  }
}

Useful tools

analyze_repo
explain_contract
build_ai_context
draft_remediation
remediate
validate_patch_diff
verify_patch
record_evidence

Why the MCP surface matters

The MCP surface makes Riven reusable as infrastructure. Another agent can explain or remediate a blocked merge request without scraping terminal output or inventing its own merge-safety logic.

The contract stays authoritative

The MCP server exposes the workflow. It does not dilute the workflow. AI output remains advisory unless the contract evidence itself changes and the gate passes.

Next: Configuration.