git-mcp-server
A Git MCP server for AI agents. STDIO & Streamable HTTP.
Runssource: GitHubhomepageTypeScriptApache-2.0commit d34d83af201d
TypeScript, Apache-2.0 licensed. The project labels itself: ai, cyanheads, enterprise ready, git, git server, git tools, mcp and mcp server.
git-mcp-server runs. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The git-mcp-server builds, all 1646 tests pass, the server launches in both STDIO and HTTP transports, the STDIO transport correctly responds to MCP initialize and tools/list requests returning 28 tool definitions, and the HTTP /healthz endpoint returns 200.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Bun not found in PATH1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- bun test exited 0, 1646 tests passed (93 files, 4705 expect calls); MCP STDIO initialize+tools/list returns 28 tools; HTTP GET /healthz returns 200; MCP initialize handshake via HTTP returns full capabilities.
- Model tokens used
- 42,943
- Exact commit tested
- d34d83af201d
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2026-09-10T10:04:54.407191Z ERROR codex_core::tools::router: error=write_stdin failed: stdin is clo… exec /bin/sh -lc 'cd /work/repo && export PATH="$HOME/.npm-global/bin:$PATH" && bun test 2>&1 | tail -5'… succeeded in 12731ms: 1646 pass 0 fail 4705 expect() calls Ran 1646 tests across 93 files. [12.83s] Confirmed: 1646 tests pass, 0 fail. Here is my final report: tokens used 42,943 Confirmed: 1646 tests pass, 0 fail. Here is my final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 2 minutes, faster than the median of the 36 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 37 ai projects Argusic has installed and timed, git-mcp-server was the 5th fastest to reach a running state, and 30 of 37 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
aicyanheadsenterprise-readygitgit-servergit-toolsmcpmcp-servermodel-context-protocol
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/git-mcp-server)Questions
- Does git-mcp-server run?
- Yes. git-mcp-server runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test git-mcp-server?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d34d83af201d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test git-mcp-server?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does git-mcp-server take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does git-mcp-server need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing git-mcp-server?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does git-mcp-server compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, git-mcp-server was the 5th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for git-mcp-server?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.