Use this page when you want to connect Codex, Claude Code, or another MCP-capable client to Prooflane’s deeper review layer without turning the product into a generic chat assistant.
Use this loop after a result already exists.
Think of it like asking a well-prepared operator to hand you the clipboard, not like opening a second control room.
Prooflane still starts from:
MCP comes in after that result path exists.
uiq_run_overviewuiq_generate_release_briefuiq_find_similar_failuresuiq_list_manual_gatesuiq_explain_template_feasibilityWhat this gives you in plain English:
uiq_run_overview tells the client what run it is looking atuiq_generate_release_brief drafts the same governed summary the UI exposesuiq_find_similar_failures finds historical failure cases that resemble the
current runuiq_list_manual_gates shows whether a paused run still needs operator helpuiq_explain_template_feasibility explains whether a reusable journey is a
good fit for another target familyThese capabilities are backed by repo-owned surfaces today:
uiq_generate_release_briefuiq_find_similar_failuresuiq_list_manual_gatesuiq_explain_template_feasibilityuiq://review/latest-release-briefuiq://manual-gates/inbox-summarySo the truthful statement is:
Prooflane works with Codex, Claude Code, and other MCP-capable clients through a governed, read-mostly MCP surface.
That is very different from claiming a native chat product or a hosted AI assistant.
{
"mcpServers": {
"uiq": {
"command": "pnpm",
"args": ["mcp:start"],
"cwd": "/ABSOLUTE/PATH/TO/REPO"
}
}
}
If you want the optional review-oriented tool groups, add:
{
"UIQ_MCP_TOOL_GROUPS": "advanced,analysis,proof"
}