server
Open source
free (OSS, MIT)

MCP Git Server

Reference MCP server for local Git repository operations. Status, diff, log, blame, branch listing — read-side operations against a checked-out repo without round-tripping to GitHub. Pairs with mcp-server-filesystem to give an agent full local-repo awareness.

By Fredoline Eruo·Last verified Jun 12, 2026·60,000 GitHub stars

Overview

Reference MCP server for local Git repository operations. Status, diff, log, blame, branch listing — read-side operations against a checked-out repo without round-tripping to GitHub. Pairs with mcp-server-filesystem to give an agent full local-repo awareness.

Stack & relationships

How MCP Git Server relates to other entries in the catalog — recommended pairings, alternatives, dependencies, and edges to avoid. Each edge carries a one-line operator note from our editorial team.

MCP Git Server ↔ ecosystem

Recommended stack

  • Pairs with
    MCP Filesystem Server

    Together they give an agent full local-repo awareness — filesystem reads files, git reads metadata (status / diff / log / blame).

Works with

  • Integrates with
    OpenHands

    Git MCP gives OpenHands repo metadata awareness — what changed, when, why. Pairs naturally with filesystem MCP for full repo grounding.

Featured in these stacks

The L3 execution stacks that pick this tool as a recommended component, with the one-line note explaining the role it plays in each.

  • Stack · L3·Workstation tier·Role: Repository state (status, diff, blame, history)
    Build a local coding-agent stack (May 2026)

    Pairs with mcp-server-filesystem to give the agent full repo awareness — read-side operations only by default. Lets OpenHands reason about what changed and why before proposing new edits.

  • Stack · L3·Workstation tier·Role: MCP git (repo metadata)
    Build a memory-enabled local agent stack (May 2026)

    Read-side git operations give the agent commit history awareness — crucial when memory says 'we tried X last session' and git can confirm whether X was actually committed or rolled back.

  • Stack · L3·Workstation tier·Role: MCP git (read-side only)
    Build a fully offline coding stack (May 2026)

    Read-side git operations give the agent commit history awareness. Combined with filesystem MCP, full repo grounding without network access.

Pros

  • Works against any local repo — no remote dependency
  • Read-side first, mutation paths gated
  • Reference implementation

Cons

  • Not a replacement for the GitHub MCP server when you need PRs/issues
  • Repo path needs to be explicitly configured

Compatibility

Operating systems
macOS
Linux
Windows
GPU backends
n/a
LicenseOpen source · free (OSS, MIT)

Runtime health

Operator-grade signals on how actively MCP Git Server is being maintained, how fresh its measurements are, and what failure classes operators have flagged. Every label below is anchored to a real date or count — we never infer maintainer activity we can't show.

Release cadence

Derived from the most recent editorial signal on this row.

Active
Updated Jun 12, 2026

8 days since last refresh · source: lastUpdated

Benchmark freshness

How recent the editorial measurements on this runtime are.

0editorial benchmarks

No editorial benchmarks for this runtime yet.

Community reproduction

Submissions that match an editorial measurement on similar hardware.

0reproduced reports

No community reproductions on file yet.

Get MCP Git Server

Frequently asked

Is MCP Git Server free?

Yes — MCP Git Server is free to use and open-source.

What operating systems does MCP Git Server support?

MCP Git Server supports macOS, Linux, Windows.

Does MCP Git Server need a GPU?

No — MCP Git Server runs on CPU; it does not require or use a GPU.

Reviewed by RunLocalAI Editorial. See our editorial policy for how we evaluate tools.

Related — keep moving

Before you buy

Verify MCP Git Server runs on your specific hardware before committing money.