All MCP Servers
Dev Tools & GitOfficial referencepypi12 toolsA · 93

Git MCP server

MIT

Read, search and manipulate Git repositories: inspect history and diffs, stage changes and commit from the conversation.

At a glance

Git is the official MCP reference server in the Dev Tools & Git category. It runs locally over stdio via `uvx mcp-server-git`, and declares no required credentials. It exposes 12 tools, including git_status, git_diff_unstaged and git_diff_staged. It scores A (93/100) on the MCP Skills Hub health score as of Oct 27, 2026.

Source 92kGitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Git in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Git in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add git -- uvx mcp-server-git
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. git_status, git_diff_unstaged, git_diff_staged). It discovers them automatically.

What tools does Git expose? (12)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

What the code can do

Source analysis currently covers npm packages only. This server ships as a Python package, which needs a different parser.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit today — Actively maintained.
  • 92k GitHub stars — Community adoption signal.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 93

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 0 days ago.

  • Adoption20%100%

    91630 stars.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%100%

    Official reference implementation, maintained by the MCP steering group.

  • Packaging15%50%

    No pinned version — installs resolve to whatever is latest at launch.

Documentation

Full README

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.

Source: https://github.com/modelcontextprotocol/servers/tree/main/src/git

Requires MCP Python SDK 2.x (mcp>=2.3,<3). The server is built on the SDK's high-level MCPServer: each tool is a typed Python function, and the SDK derives its input schema from the signature.

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
  2. Shows the working tree status
  3. Input:
  4. repo_path (string): Path to Git repository
  5. Returns: Current status of working directory as text output
  1. git_diff_unstaged
  2. Shows changes in working directory not yet staged
  3. Inputs:
  4. repo_path (string): Path to Git repository
  5. context_lines (number, optional): Number of context lines to show (default: 3)
  6. Returns: Diff output of unstaged changes
  1. git_diff_staged
  2. Shows changes that are staged for commit
  3. Inputs:
  4. repo_path (string): Path to Git repository
  5. context_lines (number, optional): Number of context lines to show (default: 3)
  6. Returns: Diff output of staged changes
  1. git_diff
  2. Shows differences between branches or commits
  3. Inputs:
  4. repo_path (string): Path to Git repository
  5. target (string): Target branch or commit to compare with
  6. context_lines (number, optional): Number of context lines to show (default: 3)
  7. Returns: Diff output comparing current state with target
  1. git_commit
  2. Records changes to the repository
  3. Inputs:
  4. repo_path (string): Path to Git repository
  5. message (string): Commit message
  6. Returns: Confirmation with new commit hash; an error if nothing is staged (as git commit without --allow-empty), except while a merge is in progress (MERGE_HEAD present), where git also allows an empty commit. While a merge is in progress the commit concludes it: its parents are HEAD and every MERGE_HEAD commit, and the merge state is cleared
  1. git_add
  2. Adds file contents to the staging area
  3. Inputs:
  4. repo_path (string): Path to Git repository
  5. files (string[]): Non-empty array of file paths to stage; ["."] stages everything
  6. Returns: Confirmation of staged files, or a message saying nothing was staged when the call left the index unchanged
  1. git_reset
  2. Unstages all staged changes
  3. Input:
  4. repo_path (string): Path to Git repository
  5. Returns: Confirmation of reset operation

Excerpt — the full document is on GitHub.

Maintain Git? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![Git on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/official-git)](https://mcp-skills-hub.vercel.app/mcps/official-git)

Catalog data refreshed . Something wrong? Report it.