Code Review Server MCP Server

Most developer tooling work still happens through a UI a human drives. Code Review Server MCP server moves it into the conversation instead. A MCP server for code reviews.

The short version

A custom MCP server that performs code reviews using Repomix and LLMs.

• Flatten codebases using Repomix
• Analyze code with Large Language Models
• Get structured code reviews with specific issues and recommendations
• Support for multiple LLM providers (OpenAI, Anthropic, Gemini)
• Handles chunking for large codebases

The tools it exposes

The server publishes 2 tools. What each one is for:

• analyze_repo — The analyze_repo tool exposed by this server
• code_review — The code_review tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Code Review Server's toolset — analyze_repo, code_review — is a fair guide to whether it matches your workflow. It is maintained by crazyrabbitLTC; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Code Review Server's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.