cc-reviewer
MCP server for Claude Code - Get second-opinion feedback from Codex/Gemini CLIs
Installation
npx cc-reviewerAsk AI about cc-reviewer
Powered by Claude Β· Grounded in docs
I know everything about cc-reviewer. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
CC Reviewer - AI Code Review for Claude Code
Get second-opinion feedback from OpenAI Codex and Google Gemini CLIs on Claude Code's work, then synthesize and incorporate.
Quick Install
Step 1: Add the MCP server
claude mcp add -s user cc-reviewer -- npx -y cc-reviewer
Step 2: Restart Claude Code
The MCP tools and slash commands (/multi-review, /multi-consult) are automatically installed.
Manual command install (if needed):
npx cc-reviewer update
Verify with:
claude mcp list
# cc-reviewer: npx -y cc-reviewer - β Connected
Alternative: Manual Install
git clone https://github.com/SimonRen/cc-reviewer.git
cd cc-reviewer/mcp-server
npm install && npm run build
claude mcp add -s user cc-reviewer -- node /path/to/cc-reviewer/mcp-server/dist/index.js
Prerequisites
Install at least one AI CLI:
# OpenAI Codex CLI
npm install -g @openai/codex-cli
codex login
# Google Gemini CLI
npm install -g @google/gemini-cli
gemini # follow auth prompts
Usage
These tools provide external second-opinion reviews from Codex and Gemini CLIs. They are designed to complement Claude Code's native review capabilities, not replace them.
When to use:
/multi-review- Get parallel standard + adversarial reviews from all available CLIs (Codex, Gemini, Claude). For reviewing CC-produced work (plan, findings, code)./multi-consult- Ask all available CLIs the same question and synthesize their answers. For consultation/Q&A β what's the best approach, how to solve X.
For regular reviews: Just say "review" and Claude Code will use its native capabilities. These external tools are only invoked when explicitly requested.
Slash Commands
These commands are available after restart:
/multi-review # Parallel standard + adversarial reviews from all CLIs
/multi-review focus on race conditions # Steer the adversarial focus
/multi-consult <question> # Ask all CLIs and synthesize
/multi-consult <question> [flex] # Use Codex flex tier (cheaper/slower)
How It Works
CC does work β User: /multi-review β External CLIs review β CC synthesizes β Final output
User has a question β User: /multi-consult β External CLIs answer β CC synthesizes β Consolidated answer
Key Principles:
- CC is primary: Claude Code does all the work; external models only review
- Working directory strategy: Pass
cwd+ small CC output; external CLIs read files directly - Synthesis, not passthrough: CC always judges external feedback before incorporating
Focus Areas
| Area | Description |
|---|---|
security | Vulnerabilities, auth, input validation |
performance | Speed, memory, efficiency |
architecture | Design patterns, structure, coupling |
correctness | Logic errors, edge cases, bugs |
maintainability | Code clarity, documentation, complexity |
scalability | Load handling, bottlenecks |
testing | Test coverage, test quality |
documentation | Comments, docs, API docs |
MCP Tools
The plugin exposes two MCP tools:
| Tool | Description |
|---|---|
multi_review | Parallel standard + adversarial review from all available CLIs (Codex, Gemini, Claude). Requires ccOutput. |
multi_consult | Ask all available CLIs the same question and receive a 5-section structured response per model. For consultation/Q&A. |
Output Format
External CLIs return structured feedback. Claude Code parses this feedback to identify:
- Findings: Issues with severity, confidence, location, and suggestions
- Agreements: Validations of CC's correct assessments
- Disagreements: Challenges to CC's claims with corrections
- Alternatives: Different approaches with tradeoffs
- Risk Assessment: Overall risk level with top concerns
Development
cd mcp-server
npm install
npm run build # Build once
npm run dev # Watch mode
npm test # Run tests
npm run test:watch # Watch mode tests
npm start # Run server
Publishing
Release-based publish via npm Trusted Publishing (OIDC, no tokens needed).
CI triggers on GitHub Release, validates the tag matches package.json.
# 1. Bump version in package.json
# 2. Rebuild and test
cd mcp-server && npm run build && npm test
# 3. Commit, tag, push, release
git add -A && git commit -m "v1.x.x"
git tag v1.x.x
git push && git push --tags
gh release create v1.x.x --title "v1.x.x" --generate-notes
License
MIT
