The git MCP server, verified live on a real Mac.

• Tools

  12, enumerated live

• Credentials

  None needed

• Transport

  stdio, runs on your Mac [6]

• Maintainer

  modelcontextprotocol [1][3]

• Downloads

  129k last week on PyPI [2]

• License

  MIT to Apache-2.0 [4]

Verification

How this MCP server was verified.

Method

We spawned the server with uvx over stdio, pointed at one throwaway repository with --repository, completed the MCP initialize handshake, called tools/list, and ran nine real tool calls: five read-only ones that succeeded, and four we expected to fail, which is where most of the troubleshooting section comes from. Nothing we called changed the repository. A second session, started with no --repository at all, produced the last error below. The plain uvx mcp-server-git command crashed before the handshake on this Mac, so both sessions used uvx --with mcp<2 mcp-server-git, which pins the Python MCP SDK to 1.29.0. The Mac ran Python 3.14.3 and uv 0.10.11. Node appears in the strip above only because our test client is a Node process; this server does not need it. The server prints nothing at all on startup, on stdout or stderr, so the banner below is the raw one-line initialize response as it came off the wire.

{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-06-18","capabilities":{"experimental":{},"tools":{"listChanged":false}},"serverInfo":{"name":"mcp-git","version":"1.29.0"}}}

tools/call git_status {"repo_path": "/private/tmp/mcp-git-demo/demo-repo"}

Repository status:
On branch main
Changes not staged for commit:

Real lines from the captured result: enough to prove the call answered.

Tools

Every tool, enumerated from the running server.

The server answered tools/list with 12 tools on 2026-08-03. The names, descriptions and parameters below are its own words, copied from that response and never edited.

Parameters marked with * are required.

Setup

Working configs, one per app.

Copy the block for the app you use. Each one is the configuration this server was verified with.

{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "--with",
        "mcp<2",
        "mcp-server-git",
        "--repository",
        "/Users/yourname/code/your-repo"
      ]
    }
  }
}

claude mcp add git -- uvx --with 'mcp<2' mcp-server-git --repository ~/code/your-repo

{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "--with",
        "mcp<2",
        "mcp-server-git",
        "--repository",
        "/Users/yourname/code/your-repo"
      ]
    }
  }
}

Name        Git
Command     uvx
Arguments   --with mcp<2 mcp-server-git --repository /Users/yourname/code/your-repo

No terminal needed

Set the Git MCP server up without the terminal.

If you have never opened Terminal and would rather keep it that way, this is your path, with one unavoidable exception noted in the first step. Routines is a Mac app that runs MCP servers for you: fill in three fields once, and this server's tools are available to your AI in chat and in scheduled routines.

1. 01

   Install Routines, and uv

   Download the app from getroutines.ai/download, drag it to Applications, and sign in. This server is Python, so it also needs uv, the tool that provides the uvx command. Install it from astral.sh/uv, or with one terminal line if you already use Homebrew: brew install uv.

2. 02

   Open the MCP settings

   Click your account at the bottom of the sidebar and choose Settings. Open the Assistant section, then the Connections tab, scroll to MCP Servers, and click Add MCP Server.

3. 03

   Choose Command (stdio)

   The form opens in URL mode. Switch it to Command (stdio): this server is a command that runs on your Mac, not a web address.

4. 04

   Point it at one repository

   Name: Git. Command: uvx. Arguments: --with mcp<2 mcp-server-git --repository followed by a space and the full path of the repository folder, like /Users/yourname/code/your-repo. Write the path in full, starting with /Users, with no spaces in it.

5. 05

   Test, then add

   Leave Environment Variables empty, this server needs none. Click Test Connection: Routines starts the server and reports how many tools it found, twelve for this one. Then click Add Server.

6. 06

   Use it

   The tools work in chat right away, so you can ask what changed in the repo this week. To let a scheduled routine use them, open the routine, find the Tools & connections card, and tick the server under Apps.

Routine ideas

Routines worth scheduling.

Once the server is connected, a scheduled routine can use its tools while you are away. Copy a prompt, paste it into Routines, and pick a time.

Troubleshooting

The errors we hit, and what fixed them.

Real errors captured during the verification run, printed exactly as the server returned them.

  File "/Users/[REDACTED]/.cache/uv/archive-v0/OwIFwgGFXK4fyeBJ7kmJc/lib/python3.14/site-packages/mcp_server_git/server.py", line 321, in serve
    @server.list_tools()
     ^^^^^^^^^^^^^^^^^
AttributeError: 'Server' object has no attribute 'list_tools'

Repository path '/private/tmp' is outside the allowed repository '/private/tmp/mcp-git-demo/demo-repo'

Ref 'no-such-branch' did not resolve to an object

/private/tmp/mcp-git-demo

FAQ

Questions people ask.

Sources

Every external claim, receipted.

Anything on this page we did not observe in the run is linked here, with the date we read it. The run itself is the receipt for the rest.

1. [1]

   PyPI registry: mcp-server-gitaccessed 2026-08-03

   Latest version 2026.7.10, published 2026-07-10; author Anthropic, PBC.; declares mcp>=1.0.0.

2. [2]

   PyPI download stats: mcp-server-gitaccessed 2026-08-03

   128,807 downloads in the last week and 758,320 in the last month at access time.

3. [3]

   GitHub: modelcontextprotocol/serversaccessed 2026-08-03

   89,142 stars and a push dated 2026-08-03 at access time, per the GitHub API.

4. [4]

   modelcontextprotocol/servers LICENSE fileaccessed 2026-08-03

   The project states it is transitioning from the MIT License to Apache-2.0; docs are CC-BY-4.0. The package metadata still declares MIT.

5. [5]

   Git server README (src/git)accessed 2026-08-03

6. [6]

   Git server source: server.pyaccessed 2026-08-03

   Creates Server("mcp-git") with no version and runs stdio_server(): the server speaks stdio and declares no version of its own.

7. [7]

   PyPI registry: mcp (the Python MCP SDK)accessed 2026-08-03

   mcp 2.0.0 was published on 2026-07-28, the release that breaks mcp-server-git 2026.7.10.

8. [8]

   modelcontextprotocol.io: Connect to local MCP serversaccessed 2026-08-03

   The Claude Desktop config file path and the mcpServers command and args shape.

9. [9]

   Claude Code docs: MCPaccessed 2026-08-03

   The claude mcp add [options] <name> -- <command> [args...] syntax for local stdio servers.

10. [10]

    Cursor docs: Model Context Protocolaccessed 2026-08-03

    The mcp.json shape and file locations.

11. [11]

    Routines: Connectorsaccessed 2026-08-03

    How Routines runs one-click OAuth connectors and any MCP server.

This page describes Git as it behaved in one dated run on one Mac. Versions move: if something here no longer matches what you see, the capture date at the top says how old the reading is.