The scope is deliberately narrow: uncommitted changes in the repository the server was launched from, which makes it a pre-commit reader rather than a PR bot. Two things follow from that. The working directory matters — start it somewhere else and it reviews someone else's diff — and the quality of the judgement is Gemini's, since this server's job is to assemble the diff and the lint output and hand them over.
A code-review server that works on local, uncommitted changes. It gathers the `git diff`, runs static analysis, hands the combined context to the Gemini CLI, and returns a structured JSON review rather than prose — so findings arrive with a file, a line and a severity attached.
- A single tool, `review-local-changes`, that finds every modified or added `.js`, `.ts`, `.tsx` and `.vue` file through `git diff` and reviews them together
- Static analysis without configuring it: the server falls back between ESLint, JSHint and the TypeScript compiler, picking the best one available in the project
- A JSON result with `summary`, `assessment` and a `findings` array — each finding carrying `filePath`, `lineNumber`, `severity`, `category`, `comment` and `suggestion`
- A clear no-op when nothing relevant changed: the tool answers "No relevant files changed" instead of inventing a review
Node.js 18 or later, npm, and Git, since the diff is collected from your working tree. You also need the Google Gemini CLI (`gemini`) installed and authenticated — the review itself runs there. The package is `code-review-mcp-server` (1.0.0 in package.json); clone, `npm install`, `npm run build`, then point your client at `dist/index.js` with `node`. Launch it from the repository root you want reviewed, because the server reads the git workspace it is started in.
One command — npx -y code-review-mcp-server