git-mcp
Put an end to code hallucinations! GitMCP is a free, open-source, remote MCP server for any GitHub project
Runssource: GitHubhomepageTypeScriptApache-2.0commit c487a29895dc
TypeScript, Apache-2.0 licensed. The project labels itself: agentic ai, agents, ai, claude, copilot, cursor, git and llm.
git-mcp runs. An Argusic agent installed it in 1 minute and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install succeeded, all 37 vitest tests pass, the production build compiles without errors, and the wrangler dev server starts on port 8794 serving the GitMCP web app (200 on /), the Shields badge endpoint (200 on /badge/*), and the MCP SSE protocol (200 on POST /:owner/:repo with proper initialize handshake returning server name and capabilities).
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.
- Node.js v18 detected but react-router and wrangler recommend v20+
- Install time
- 1 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- `npx pnpm test` exited 0, 7 test files, 37 passed; `npx pnpm build` completed; `npx pnpm start --port 8794` launched wrangler dev server on localhost:8794, GET / returned 200 with `<title>GitMCP</title>`, GET /badge/owner/repo returned 200 with valid Shields JSON, POST to /mrdoob/three.js with Accept: application/json, text/event-stream returned 200 with valid MCP initialize response including `serverInfo:{name:"GitMCP",version:"1.1.0"}` and `capabilities:{tools:{listChanged:true}}`, OPTIONS returned 204 for CORS preflight, /.well-known/oauth-protected-resource returned 404 as designed
- Model tokens used
- 99,125
- Exact commit tested
- c487a29895dc
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 30871ms:
✓ src/api/tools/repoHandlers/threejs/utils.test.ts (1 test) 16ms
✓ src/api/tools/commonTools.test.ts (4 tests) 5ms
✓ src/test/badge.test.ts (1 test) 56ms
Test Files 7 passed (7)
Tests 37 passed (37)
Start at 22:36:07
Duration 2.52s (transform 1.29s, setup 0ms, collect 3.13s, tests 133ms, environment 2ms, prepar…
All verified. Here is the final report:
tokens used
99,125
All verified. Here is the 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 1 minute, faster than the median of the 7 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.
- Measured 2 times, so the result is not a one-off.
Of the 8 agentic-ai projects Argusic has installed and timed, git-mcp was the 1st fastest to reach a running state, and 5 of 8 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 1 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/git-mcp)Questions
- Does git-mcp run?
- Yes. git-mcp runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test git-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c487a29895dc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test git-mcp?
- The run that produced this verdict cost $0.08: 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 take to install?
- 1 minute 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 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing git-mcp?
- 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 compare with the alternatives?
- Of the 8 agentic-ai projects Argusic has installed and timed, git-mcp was the 1st fastest to reach a running state, and 5 of 8 reached one at all.
- Where is the evidence for git-mcp?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.