Skip to main content
Glama
Git Code Review MCP
by AyoubTRD

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:

{
  "mcpServers": {
    "git-codereview": {
      "command": "npx",
      "args": ["git-codereview"]
    }
  }
}

Related MCP server: GitHub Repo Explainer MCP

Installation

The easiest way to use this MCP server is with npx:

npx git-codereview

This will run the MCP server directly without needing to install it globally.

Alternative Installation Methods

Global Installation

npm install -g git-codereview
git-codereview

Local Development

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.

Available Tools

3 tools
get_diffGet DiffC

Retrieve the diff of staged files in a git repository

Inputs: repoPath (required).

get_file_contentGet File ContentA

Retrieve the content of a file in a git repository. Use it when the diff doesn't provide enough context.

Inputs: repoPath (required), filePath (required).

get_staged_filesGet Staged FilesC

Retrieve the list of staged files in a git repository

Inputs: repoPath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with local Git repositories for operations like status, commits, branching, and diffs, plus GitHub API integration for managing pull requests when authenticated.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access live GitHub repository data without cloning, supporting repo summarization, file explanation, recent changes, and dependency analysis.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.
      10
      145 npm
      ISC
    • A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.
      13
      1
      MIT