rigour — Claude Code MCP server: review what the agent wrote
Checks an agent's edits against your repository rules and what the team has learned. Useful when the agent writes faster than anyone can review.
claude mcp add rigour -- npx -y @rigour-labs/mcpWhat rigour does
Rigour attaches to a coding agent as an MCP server and gets in the way at three points. Editing a file triggers quick checks: secrets, imports that resolve to nothing, bugs already known. Before the agent reports success, the whole branch is compared with main. Ahead of git push your own formatter, linter, type check and tests join in — a failing push is refused, one line per problem.
Briefing works differently. On a file's first edit the agent receives at most three cited points drawn from what your repo already declares: AGENTS.md, CLAUDE.md, Cursor rules, Copilot instructions. Team lessons are added only on evidence — a person corrected the agent, a teammate made a call, the same slip showed up across authors. A guess never turns into a rule.
The reviewer stays off until you enable it in Studio or rigour.yml. Once on, it reads the points from your last human review and follows your Blocking / Should fix / Nits labels over its own judgement. Profiles keep one employer's or client's memory separate from another's on the same machine, picked by the repository you open. To look before installing, npx @rigour-labs/cli review --base origin/main reports findings and leaves the tree alone.
What it helps with
- catch a secret in a file before the agent commits it
- spot merge conflicts and dead code on the branch before the agent says it is done
- stop a push when tests, lint or type check fail
- hand the agent the rules for one file before its first edit
- keep client A's lessons away from client B's on one machine
Example prompts for the agent
- Brief me on
src/api/orders.tsbefore you touch it - Compare this branch with
origin/mainand tell me what blocks the push - Show the full thread for this task: what got caught and what got fixed
How to install rigour
Platform CLI
claude mcp add rigour -- npx -y @rigour-labs/mcpPlatform CLI
codex mcp add rigour -- npx -y @rigour-labs/mcpConfig file
{
"mcpServers": {
"rigour": {
"command": "npx",
"args": [
"-y",
"@rigour-labs/mcp"
]
}
}
}Config file
{
"servers": {
"rigour": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@rigour-labs/mcp"
]
}
}
}Platform CLI
gemini mcp add rigour npx -y @rigour-labs/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about rigour
How do I install rigour in Claude Code?
Run claude mcp add rigour -- npx -y @rigour-labs/mcp. That registers the server in your Claude config, and npx starts it from then on.
What does rigour do?
It tells the agent what your repo expects of a given file, checks edits at three stages, and refuses the push when your own tools fail. The reviewer is a separate switch and leans on your team's earlier comments.
How is it different from a normal code review?
Rigour never retrains or alters the model; it works from your rules files and from decisions the team already made. Design taste stays with people — anything it cannot show in code never rises above should-fix.
