@1key4ai/mcp-review

Plan review for Claude Code via 1K4.

Two or more AI models review your implementation plans and return structured findings with severity and evidence. Setup is one command; reviews run automatically during plan mode.

Setup

1. Get your API key at 1key4ai.com/claude-code
2. Run the setup command:

npx -y -p @1key4ai/mcp-review mcp-review setup --api-key YOUR_KEY

This registers the MCP server, adds a /review-plan skill, and configures Claude Code to review plans automatically. Works globally across all your projects.

For staging:

npx -y -p @1key4ai/mcp-review mcp-review setup --api-key YOUR_KEY --api-base https://staging.1key4ai.com

Or add to your MCP config manually:

{
  "mcpServers": {
    "1k4-review": {
      "command": "npx",
      "args": ["-y", "-p", "@1key4ai/mcp-review", "mcp-review"],
      "env": {
        "K4_API_KEY": "your-key-here"
      }
    }
  }
}

What happens

After setup, Claude Code automatically reviews plans before presenting them for approval. Multi-model reviewers (Gemini, GPT, Grok) return findings at three severities: critical (ship-blocker), important (correctness gap), advisory (style). Claude Code synthesizes findings and iterates until consensus. Say "skip review" to opt out for any specific plan.

Tools included

This package now ships the full unified 1K4 surface:

• 1k4_review_plan: Multi-model plan review with structured findings
• 1k4_advisors: List available advisor personas and their capabilities
• 1k4_consult: Ask a single AI advisor a freeform question (code review, security audit, design feedback)
• 1k4_brainstorm: Multi-round, multi-advisor brainstorm with cross-pollination
• 1k4_send_message / 1k4_wait_for_message / 1k4_get_session_status / 1k4_list_files / 1k4_get_file / 1k4_answer_questionnaire: Studio agent bridge
• lab_create_file / lab_edit_file / lab_read_file / lab_list_files / lab_create_folder / lab_move_file / lab_create_document / lab_edit_document / lab_create_presentation / lab_create_mockup / lab_git / lab_review_document / lab_update_file / lab_vm_ops / lab_deploy / lab_questionnaire / lab_web_fetch / lab_data_analysis: Lab workspace operations
• Plus dynamically-discovered tools from the backend catalog

Two install paths (mcp-review vs cc-bridge)

Starting with version 0.6.0, @1key4ai/mcp-review ships the same full unified tool surface as @1key4ai/cc-bridge. Both packages re-export the same compiled MCP server. The only difference is the entry written to ~/.claude.json:

| Package | mcpServers key | Tool prefix in Claude Code | |---|---|---| | @1key4ai/mcp-review | 1k4-review | mcp__1k4-review__1k4_review_plan etc. | | @1key4ai/cc-bridge | 1k4-bridge | mcp__1k4-bridge__1k4_review_plan etc. |

Existing mcp-review users — nothing to do

Your ~/.claude.json already has mcpServers["1k4-review"] with args: ["-y", "-p", "@1key4ai/mcp-review@latest", "mcp-review"]. The @latest pin means npx resolves the registry on every Claude Code session start — when 0.6.0 publishes, your next CC session picks up the expanded tool surface automatically. No re-run of setup required. Tool prefixes stay mcp__1k4-review__* (no client-side breakage).

New users — recommended: cc-bridge

If you're starting fresh, install @1key4ai/cc-bridge instead:

npx -y -p @1key4ai/cc-bridge@latest cc-bridge setup --api-key YOUR_KEY

The cc-bridge entry uses the cleaner short args form (["-y", "@1key4ai/cc-bridge@latest"]) and serves as the marketing name for the unified product going forward.

Migrating mcp-review → cc-bridge (optional)

To consolidate your existing 1k4-review entry into a single 1k4-bridge entry:

npx -y -p @1key4ai/cc-bridge@latest cc-bridge setup

cc-bridge setup detects the existing 1k4-review (and 1k4-lab/1k4-studio if present), prompts Proceed? [y/N], backs up ~/.claude.json to a timestamped file, and writes a single mcpServers["1k4-bridge"] entry preserving your captured env vars. Migration is opt-in; skip it and mcp-review keeps working indefinitely.

Your first review is free

2 rounds, on us.

Pricing

Pay per token at below list price. Credits never expire.