Git Mcp Server

What is Git Mcp Server about?

Git Mcp Server is a Model Context Protocol (MCP) server that exposes common Git commands as callable tools for AI assistants. It can monitor one or multiple repositories, execute operations via the native Git CLI or the pure‑Go go-git library, and optionally allow write‑access for actions such as git push.

How to use Git Mcp Server?

1. Installation – Build from source with Go (go build -o git-mcp-go .) or download a pre‑built binary from the GitHub Releases page.
2. Running the server – Use the serve sub‑command, specifying repository paths with -r/--repository or as positional arguments. Example:

   ./git-mcp-go serve -v -r=/path/to/repo1,/path/to/repo2 --mode shell
   

   Add --write-access to enable remote‑modifying tools like git_push.
3. Setup for an AI assistant – Run the setup sub‑command; it copies the binary to the assistant’s MCP directory and creates a registration script. Example:

   ./git-mcp-go setup -r=/path/to/repo1,/path/to/repo2 --auto-approve=allow-read-only
   

4. Tool invocation – AI assistants call tools such as git_status, git_diff, git_commit, etc., passing optional repo_path when multiple repositories are configured.

Key features of Git Mcp Server

• Comprehensive Git toolset: status, diff (unstaged, staged, arbitrary commits), log, commit, add, reset, branch creation, checkout, show, init, push, repository listing.
• Multi‑repository support: monitor and operate on several repos simultaneously.
• Two implementation modes:
  • shell (default) – runs native Git commands.
  • go-git – uses the Go library for faster, dependency‑free operations where possible.
• Fine‑grained write access control – --write-access flag required for any operation that changes remote state.
• Auto‑approval configuration – pre‑approve read‑only or local‑only tools, or specify a custom list.
• Cross‑platform binaries – Linux, macOS, Windows (amd64 & arm64).
• CI‑driven testing – tests run in both modes against temporary repositories.

Use cases of Git Mcp Server

• AI‑assisted code review – an assistant can call git_diff and git_log to summarize changes.
• Automated repository maintenance – scripts can trigger git_add, git_commit, and git_push without manual CLI interaction.
• Multi‑repo orchestration – manage several micro‑service repos from a single AI‑driven workflow.
• Learning environments – students can query repository state via natural language prompts.
• Integration with Claude, Cline, or other LLM‑powered tools – provides a standardized MCP interface for Git operations.

FAQ from the Git Mcp Server

• Do I need Git installed? Yes, the shell mode relies on the Git CLI; the go-git mode only requires Go libraries.
• Can I run the server without write access? Absolutely; write‑modifying tools are disabled by default for safety.
• How does the server choose a repository when multiple are configured? If a command does not specify repo_path, the first repository in the list is used as the default.
• Which mode should I use? shell offers full Git compatibility; go-git is faster and avoids external dependencies but may lack some edge‑case features.
• How do I update the server? Download the latest binary from the releases page or rebuild from the latest source and replace the existing executable.
• Is there a way to auto‑approve tools? Yes, use --auto-approve=allow-read-only, allow-local-only, or provide a comma‑separated list of tool names.
• Can I integrate this with other MCP servers? The MCP protocol is language‑agnostic; you can register multiple servers under different names in your assistant’s configuration.

Git MCP Server (Go)

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

Features

This MCP server provides the following Git operations as tools:

• git_status: Shows the working tree status
• git_diff_unstaged: Shows changes in the working directory that are not yet staged
• git_diff_staged: Shows changes that are staged for commit
• git_diff: Shows differences between branches or commits
• git_commit: Records changes to the repository
• git_add: Adds file contents to the staging area
• git_reset: Unstages all staged changes
• git_log: Shows the commit logs
• git_create_branch: Creates a new branch from an optional base branch
• git_checkout: Switches branches
• git_show: Shows the contents of a commit
• git_init: Initialize a new Git repository
• git_push: Pushes local commits to a remote repository (requires --write-access flag)
• git_list_repositories: Lists all available Git repositories

Installation

Prerequisites

• Go 1.18 or higher
• Git installed on your system

Download Prebuilt Binaries

You can download prebuilt binaries for your platform from the GitHub Releases page.

Building from Source

# Clone the repository
git clone https://github.com/geropl/git-mcp-go.git
cd git-mcp-go

# Build the server
go build -o git-mcp-go .

Install with go install

go install github.com/geropl/git-mcp-go@latest

Usage

Command Line Structure

The Git MCP Server uses a command-line structure with subcommands:

git-mcp-go
├── serve [flags] [repository-paths...]
│   ├── --repository, -r <paths>                  # Repository paths (multiple ways to specify)
│   ├── --mode <shell|go-git>
│   ├── --write-access
│   └── --verbose, -v
└── setup [flags] [repository-paths...]
    ├── --repository, -r <paths>                  # Repository paths (multiple ways to specify)
    ├── --mode <shell|go-git>
    ├── --write-access
    ├── --auto-approve <tool-list|allow-read-only|allow-local-only>
    └── --tool <cline,roo-code>

Multi-Repository Support

The Git MCP Server can now monitor and operate on multiple repositories simultaneously. You can specify repositories in several ways:

1. Using the -r/--repository flag:
   • With comma-separated paths: -r=/path/to/repo1,/path/to/repo2
   • With multiple flag instances: -r=/path/to/repo1 -r=/path/to/repo2
2. As positional arguments: serve /path/to/repo1 /path/to/repo2
3. A combination of both approaches

When using multiple repositories, the server will default to the first repository for operations where a specific repository is not specified.

serve Command

The serve command starts the Git MCP server:

# Run with verbose logging
./git-mcp-go serve -v /path/to/repo1 /path/to/repo2 /path/to/repo3

# Run with go-git implementation
./git-mcp-go serve --mode go-git -r=/path/to/repo1,/path/to/repo2

# Enable write access for remote operations
./git-mcp-go serve -r=/path/to/repo1,/path/to/repo2 --write-access

The --mode flag allows you to choose between two different implementations:

• shell: Uses the Git CLI commands via shell execution (default)
• go-git: Uses the go-git library for Git operations where possible

The --write-access flag enables operations that modify remote state (currently only the push operation). By default, this is disabled for safety.

setup Command

The setup command sets up the Git MCP server for use with an AI assistant. It copies itself to ~/mcp-servers/git-mcp-go and modifies the tools config (cline: cline_mcp_settings.json) to use that binary.

# Set up for Cline with a single repository
./git-mcp-go setup -r /path/to/git/repository

# Set up with repositories as arguments
./git-mcp-go setup /path/to/repo1 /path/to/repo2 /path/to/repo3

# Set up with write access enabled
./git-mcp-go setup -r=/path/to/repo1,/path/to/repo2 --write-access

# Set up with auto-approval for read-only tools
./git-mcp-go setup -r=/path/to/repo1,/path/to/repo2 --auto-approve=allow-read-only

# Set up with specific tools auto-approved
./git-mcp-go setup -r=/path/to/repo1,/path/to/repo2 --auto-approve=git_status,git_log

# Set up with write access and auto-approval for read-only tools
./git-mcp-go setup -r=/path/to/repo1,/path/to/repo2 --write-access --auto-approve=allow-read-only

The --auto-approve flag allows you to specify which tools should be auto-approved (not require explicit user approval):

• allow-read-only: Auto-approve all read-only tools (git_status, git_diff_unstaged, git_diff_staged, git_log, git_show, git_diff)
• allow-local-only: Auto-approve all local-only tools (incl. git_commit, git_add, git_reset, but not git_push)
• comma-separated list: Auto-approve specific tools (e.g., git_status,git_log)

Repository Management

The git_list_repositories Tool

This tool lists all available Git repositories that the server is monitoring. It shows:

• The total number of repositories
• The path to each repository
• The repository name (derived from the directory name)

Example output:

Available repositories (3):

1. repo1 (/path/to/repo1)
2. repo2 (/path/to/repo2)
3. another-project (/path/to/another-project)

Repository Selection

When running commands that require a repository path:

1. If a specific repo_path is provided in the command, it will be used.
2. If no repo_path is provided and multiple repositories are configured, the first repository will be used as the default.
3. Each command output will indicate which repository was used for the operation.

Installation

Automatic Installation and Configuration

The easiest way to install and register the Git MCP server with Cline is to use the setup command:

# Download linux binary for the latest release
RELEASE="$(curl -s https://api.github.com/repos/geropl/git-mcp-go/releases/latest)"
DOWNLOAD_URL="$(echo $RELEASE | jq -r '.assets[] | select(.name | contains("linux-amd64")) | .browser_download_url')"
curl -L -o ./git-mcp-go $DOWNLOAD_URL
chmod +x ./git-mcp-go

# Setup the mcp server with a single repository
./git-mcp-go setup -r /path/to/git/repository --tool=cline --auto-approve=allow-local-only

# Setup the mcp server with multiple repositories
./git-mcp-go setup -r=/path/to/repo1,/path/to/repo2 --tool=cline --auto-approve=allow-local-only

rm -f ./git-mcp-go

The setup command will:

1. Copy the executable to the Cline MCP directory
2. Create a registration script that configures Cline to use the Git MCP server

Manual Configuration

Alternatively, you can manually add this to your claude_desktop_config.json:

"mcpServers": {
  "git": {
    "command": "/path/to/git-mcp-go",
    "args": ["serve", "-r=/path/to/repo1,/path/to/repo2", "--mode", "shell"]
  }
}

"mcpServers": {
  "git": {
    "command": "/path/to/git-mcp-go",
    "args": ["serve", "-r", "/path/to/git/repository"]
  }
}

Implementation Details

This server is implemented using:

• mcp-go: Go SDK for the Model Context Protocol
• go-git: Pure Go implementation of Git (used for the go-git mode)

For operations not supported by go-git, the server falls back to using the Git CLI.

Development

Testing

The server includes comprehensive tests for all Git operations. The tests are designed to run against both implementation modes:

# Run all tests
go test ./pkg -v

# Run specific tests
go test ./pkg -v -run TestGitOperations/push

The test suite creates temporary repositories for each test case and verifies that the operations work correctly in both modes.

Continuous Integration

This project uses GitHub Actions for continuous integration and deployment:

• Automated tests run on every pull request to the main branch
• Releases are created when a tag with the format v* is pushed
• Each release includes binaries for multiple platforms:
  • Linux (amd64, arm64)
  • macOS (amd64, arm64)
  • Windows (amd64)

To create a new release:

# 1. Update the version in pkg/server.go (line ~26)
# Edit the version string in NewGitServer function

# 2. Commit the version change
git add pkg/server.go
git commit -m "Bump version to v1.3.1"

# 3. Push the commit
git push origin main

# 4. Tag the current commit
git tag v1.3.1

# 5. Push the tag to GitHub (this triggers the release)
git push origin v1.3.1

License

This project is licensed under the MIT License.