Created: 2026 August 13

mcp-git

Table of Contents

1.0 Overview 2.0 Installation 2.1 Development install 2.2 De-installation 3.0 Configuration 4.0 Tools Version History

Related MCP server: local-code-mcp

1.0 Overview

A local git MCP server. It exposes 12 git operations to an MCP client (e.g. Claude Desktop or Claude Code) over stdio, so the client can inspect and work with a git repository on your machine — status, diffs, log, branches, staging, and commits.

Return to Table of Contents

2.0 Installation

Requires Python 3.9+. Installs the latest release into its own virtual environment at ~/.local/share/mcp-git/venv — no clone required:

curl -fsSL https://raw.githubusercontent.com/William12556/mcp-git/main/bin/install.sh | bash

The script prints the full path to the installed mcp-git command when it finishes — use that path in your MCP client configuration (§3.0).

To confirm it installed correctly:

~/.local/share/mcp-git/venv/bin/python -c "import mcp_git; print(mcp_git.__version__)"

2.1 Development install

To work on mcp-git itself (run tests, use bin/build.sh / bin/release.sh), clone the repository instead:

git clone https://github.com/William12556/mcp-git.git
cd mcp-git
python3 -m venv venv
source venv/bin/activate
pip install -e .[dev]

Return to Table of Contents

2.2 De-installation

Remove the install directory:

rm -rf ~/.local/share/mcp-git

If the MCP_GIT_HOME environment variable was set to a non-default location during installation, remove that directory instead. Then remove the mcp-git entry from your MCP client configuration (§3.0).

For a development install, remove the cloned repository directory in place of the above.

Return to Table of Contents

3.0 Configuration

Add mcp-git to your MCP client's configuration, pointing at the installed console script. For Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "git": {
      "command": "/Users/<you>/.local/share/mcp-git/venv/bin/mcp-git"
    }
  }
}

Use the full path printed by the install script (or, for a development install, the venv you created). No startup arguments are needed — every tool call takes its own repo_path, so one server instance can work with any repository on your machine.

Return to Table of Contents

4.0 Tools

Every tool operates only on the repository at the repo_path you give it — nothing outside that path is touched, and mcp-git makes no network calls.

Return to Table of Contents

Version History

Copyright (c) 2026 William Watson. MIT License.