mcp-server-git: A git MCP server

Overview

A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models.

Please note that mcp-server-git is currently in early development. The functionality and available tools are subject to change and expansion as we continue to develop and improve the server.

Tools

1. git_status
   • Shows the working tree status
   • Input:
     • repo_path (string): Path to Git repository
   • Returns: Current status of working directory as text output
2. git_diff_unstaged
   • Shows changes in working directory not yet staged
   • Input:
     • repo_path (string): Path to Git repository
   • Returns: Diff output of unstaged changes
3. git_diff_staged
   • Shows changes that are staged for commit
   • Input:
     • repo_path (string): Path to Git repository
   • Returns: Diff output of staged changes
4. git_diff
   • Shows differences between branches or commits
   • Inputs:
     • repo_path (string): Path to Git repository
     • target (string): Target branch or commit to compare with
   • Returns: Diff output comparing current state with target
5. git_commit
   • Records changes to the repository
   • Inputs:
     • repo_path (string): Path to Git repository
     • message (string): Commit message
   • Returns: Confirmation with new commit hash
6. git_add
   • Adds file contents to the staging area
   • Inputs:
     • repo_path (string): Path to Git repository
     • files (string[]): Array of file paths to stage
   • Returns: Confirmation of staged files
7. git_reset
   • Unstages all staged changes
   • Input:
     • repo_path (string): Path to Git repository
   • Returns: Confirmation of reset operation
8. git_log
   • Shows the commit logs
   • Inputs:
     • repo_path (string): Path to Git repository
     • max_count (number, optional): Maximum number of commits to show (default: 10)
   • Returns: Array of commit entries with hash, author, date, and message
9. git_create_branch
   • Creates a new branch
   • Inputs:
     • repo_path (string): Path to Git repository
     • branch_name (string): Name of the new branch
     • start_point (string, optional): Starting point for the new branch
   • Returns: Confirmation of branch creation
10. git_checkout
    • Switches branches
    • Inputs:
      • repo_path (string): Path to Git repository
      • branch_name (string): Name of branch to checkout
    • Returns: Confirmation of branch switch
11. git_show
    • Shows the contents of a commit
    • Inputs:
      • repo_path (string): Path to Git repository
      • revision (string): The revision (commit hash, branch name, tag) to show
    • Returns: Contents of the specified commit

Installation

Using uv (recommended)

When using uv no specific installation is needed. We will use uvx to directly run mcp-server-git.

Using PIP

Alternatively you can install mcp-server-git via pip:

After installation, you can run it as a script using:

Configuration

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

Usage with Zed

Add to your Zed settings.json:

Debugging

You can use the MCP inspector to debug the server. For uvx installations:

Or if you've installed the package in a specific directory or are developing on it:

Running tail -n 20 -f ~/Library/Logs/Claude/mcp*.log will show the logs from the server and may help you debug any issues.

Development

If you are doing local development, there are two ways to test your changes:

1. Run the MCP inspector to test your changes. See Debugging for run instructions.
2. Test using the Claude desktop app. Add the following to your claude_desktop_config.json:

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.