review-flow

Reviewflow runs an automated AI code review workflow that can be triggered from your GitLab or GitHub repositories. The MCP integration provided by the server allows Claude Code to interact with the review process through structured tools such as get_workflow, start_agent, complete_agent, set_phase, get_threads, and add_action. Use the dashboard to monitor live progress, view agent results, and follow up automatically when developers push fixes. This setup enables multi-agent reviews (e.g., Clean Architecture, Security, Testing) and provides a real-time, WebSocket-enabled dashboard to observe phase transitions, agent status, and review history. The server is designed to work with both GitLab and GitHub, using secure CLI-based OAuth for authentication instead of embedding API tokens.

To use Reviewflow with MCP, ensure your MCP server is running and reachable by webhook callbacks. The MCP tools allow Claude to report progress, advance review phases, fetch discussion threads, and queue thread actions such as resolving, replying, or commenting. When a developer pushes new changes that address blocking issues, Reviewflow can re-read threads, verify resolutions, and post follow-up summaries with updated scores, creating an iterative review loop.

Prerequisites:

• Node.js >= 20 installed on the host machine
• npm (comes with Node.js) or pnpm/yarn if preferred
• GitHub or GitLab project with webhooks support and access configured

Installation steps:

1. Install the Reviewflow CLI globally (example):

npm install -g reviewflow

2. Initialize or configure your project for MCP integration (interactive):

reviewflow init

• Follow prompts to configure server port, webhook secrets, and MCP integration with Claude Code.
• For non-interactive setup, use: reviewflow init --yes

3. Start the Reviewflow server:

reviewflow start

• The dashboard will be available at http://localhost:3847 by default (adjust via configuration).

4. Validate your setup:

reviewflow validate

5. If you already have a running MCP server, ensure its configuration matches the provided mcp_config and environment variables.

Tips and common issues:

• Ensure Node.js version matches the project requirements (Node.js >= 20).
• Keep WEBHOOK_SECRET secure; rotate periodically and update in both your MCP config and repository settings.
• If the MCP server cannot connect to Claude Code, check network permissions, API keys, and that the MCP port is accessible from the webhook delivery path.
• The dashboard uses WebSocket; ensure your environment allows WebSocket connections through firewalls.
• When updating config, restart the MCP server to apply changes.
• If you encounter credential issues with GitHub/GitLab, rely on the OAuth flow via CLI tools (gh/glab) as documented; no token in config files.
• Reviewflow’s agents are configurable; you can tailor the agent list to match your project standards by editing the agents block in the project configuration.
• For troubleshooting, consult the CLI reference and deployment guide linked in the Documentation section of the README.