Git Code Review MCP
# Git Code Review MCP
An MCP (Model Context Protocol) server that allows AI to review your changes before pushing. This tool provides AI assistants with access to git repository information, staged files, and diffs to help with code review workflows.
## Features
- **Get Staged Files**: List all files currently staged for commit
- **View Diffs**: Show the diff of staged changes with space-change filtering
- **File Content Access**: Retrieve the content of any file from the repository
- **Repository Agnostic**: Works with any git repository by specifying the path
### Example MCP Client Configuration
If you're using this with an MCP client, add it to your configuration:
```json
{
"mcpServers": {
"git-codereview": {
"command": "npx",
"args": ["git-codereview"]
}
}
}
```
## Installation
The easiest way to use this MCP server is with npx:
```bash
npx git-codereview
```
This will run the MCP server directly without needing to install it globally.
### Alternative Installation Methods
#### Global Installation
```bash
npm install -g git-codereview
git-codereview
```
#### Local Development
```bash
git clone https://github.com/AyoubTRD/git-codereview-mcp.git
cd git-codereview-mcp
npm install
npm run build
node build/index.js
```
## Usage
This MCP server runs over stdio and is designed to be used with MCP-compatible AI tools. The server provides three main tools:
### Available Tools
1. **get_staged_files**
- Lists all files currently staged for commit
- Requires: `repoPath` (full path to git repository)
2. **get_diff**
- Shows the diff of staged files with added/modified filter
- Ignores whitespace changes for cleaner output
- Requires: `repoPath` (full path to git repository)
3. **get_file_content**
- Retrieves the content of any file from the repository
- Useful when diff doesn't provide enough context
- Requires: `repoPath` (full path to git repository) and `filePath` (relative path to file)
## Requirements
- Node.js (version 16 or higher)
- Git repository (the target repository must be git-initialized)
- MCP-compatible AI tool or client
## License
ISC
## Contributing
Issues and pull requests are welcome at [GitHub](https://github.com/AyoubTRD/git-codereview-mcp).TDQS
Scored across 3 tools
The tools have distinct purposes: get_diff retrieves diff content, get_file_content provides full file content for context, and get_staged_files lists staged files. While get_diff and get_file_content could be confused for overlapping file content retrieval, the descriptions clarify that get_file_content is for supplemental context when diff is insufficient, maintaining reasonable separation.
All tool names follow a consistent verb_noun pattern with 'get_' prefix: get_diff, get_file_content, get_staged_files. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming style.
With only 3 tools, the set feels thin for a code review domain, which typically involves more operations like commenting, approving, or managing reviews. While the tools cover basic retrieval needs, the count is borderline low for the apparent scope, limiting functionality.
The tool set is severely incomplete for code review workflows. It only provides retrieval operations (get_diff, get_file_content, get_staged_files) but lacks essential actions like creating comments, submitting reviews, or managing pull requests. This creates significant gaps that will cause agent failures in performing full code review tasks.