@genius-revius/mcp
v0.1.0
Published
MCP server (stdio) for [Revius](../../README.md) -- exposes review session data, findings, generated artifacts, and review packs to Claude Code and other MCP-compatible clients.
Readme
@genius-revius/mcp
MCP server (stdio) for Revius -- exposes review session data, findings, generated artifacts, and review packs to Claude Code and other MCP-compatible clients.
Install
npm install -g @genius-revius/mcpUsage
Register the server with your MCP client (stdio transport), pointing it at a repo that has Revius initialized (a .revius/ directory with a SQLite database):
{
"mcpServers": {
"revius": {
"command": "revius-mcp",
"args": ["--revius-dir", "/path/to/project/.revius"]
}
}
}--revius-dir defaults to .revius (resolved from the process cwd) and can also be set via the REVIUS_DIR environment variable.
Tools
| Tool | Description |
|------|-------------|
| revius_sessions | List recent review sessions with observation counts |
| revius_findings | Get findings (observations) from a session, filterable by severity |
| revius_tasks | Get generated tasks.md content from a session |
| revius_prompts | Get generated prompts.md content from a session |
| revius_summary | Get observation counts and severity breakdown across all sessions |
| revius_pack_list | List available review packs |
| revius_pack_apply | Apply a review pack to a session and return the findings report |
See the main README for full documentation.
MCP protocol version
This server is built on @modelcontextprotocol/sdk
and negotiates the stable 2025-11-25 MCP specification (the SDK falls back to
older revisions — down to 2024-11-05 — for clients that request them). The SDK owns
the JSON-RPC lifecycle, so notifications/initialized and other notifications are
correctly ignored instead of being answered with an error.
RC 2026-07-28 policy
The 2026-07-28 Release Candidate (frozen 2026-05-21, final 2026-07-28) introduces a
stateless core, an Extensions framework, and full JSON Schema 2020-12. We deliberately
target the stable 2025-11-25 spec, not the RC, because:
- Stable
2025-11-25is normative and supported today; the RC can still shift until 28/07. - RC clients stay backward-compatible with a
2025-11-25server (they fall back to theinitializehandshake), so there is no urgency to adopt the stateless core. - This server runs over stdio — the RC's remote/auth/load-balancer changes do not apply.
RC conformance (stateless core, server/discover, load-balancer headers) is deferred
until after 2026-07-28 and will be re-evaluated only if Revius is ever exposed over
Streamable HTTP. The SDK dependency is bounded <2 (^1.29.0) to avoid an accidental
jump to the SDK v2 line before that review. See
decisions/MCP-SPEC-REFERENCE-2026-07.md for the full rationale.
