About Gi
Gi is an MCP server and CLI for developers and coding agents to query Git history by line, file, or branch, including ownership, related changes, and pull request context.
Key features
- 01Group line blame by author
- 02Link lines or commits to PRs
- 03Find files changed together
- 04Inspect branch status and staleness
- 05Summarize an author's recent work
- 06Retrieve commit and issue context
Use cases
- 01Identify owners of code regions
- 02Find the PR that introduced a line
- 03Spot branches that need cleanup
- 04Prepare a summary of recent commits
MCP support
Runs as a stdio MCP server and exposes semantic Git history tools to MCP-compatible clients. GitHub PR and issue lookups require a GitHub token; local Git tools work without one.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README
git-insight-mcp
Semantic git queries via MCP. Beyond git log — answer who/what/when/why about any line, file, or branch.

Pairs with terminal-history-mcp and localhost-mcp. Together: what you ran, what's running, what you changed.
Why
Devs ask these constantly; git answers poorly:
- "Who last touched this function?" —
git blameonly gives lines, not authors-by-region - "What PR introduced this line?" — manual: blame → commit SHA → search GH
- "Which files always change together?" — no built-in
- "Show unmerged branches older than 30 days" — bash one-liner gymnastics
- "What did I work on last week?" — manual log scrub
LLM agents need this context to make safe edits. Currently they git log -n 5 and miss everything.
Install
npm install -g git-insight-mcp
Wire into Claude Code:
claude mcp add --scope user git-insight -- git-insight-mcp
Or any MCP-compatible client. Runs as a stdio MCP server.
For PR / issue lookups, set a GitHub token:
export GH_TOKEN=ghp_...
Without a token, the local-git tools still work. PR linkage is skipped.
Tools
| Tool | Purpose |
|---|---|
who_touched | Group blame by author. Lines, commits, last-touched, primary owner. Optional line-range narrowing. |
introducing_pr | Find the PR that introduced a line (or commit). Parses merge messages first; falls back to GitHub API. |
co_change | Files most often changed together with the input file. |
branch_hygiene | List branches with ahead/behind, last commit, merged status, stale flag. |
recent_work | Standup helper: author's commits + files + ins/del in a window. |
commit_context | Full commit context: subject, body, files, PR, related issues. |
Sample output (who_touched)
{
"file": "src/auth.ts",
"total_lines": 124,
"authors": [
{ "name": "alice", "email": "[email protected]", "lines": 87, "commits": 12, "last_commit_date": "2026-04-12T10:33:01.000Z" },
{ "name": "bob", "email": "[email protected]", "lines": 37, "commits": 4, "last_commit_date": "2026-01-03T18:14:55.000Z" }
],
"primary_owner": "alice"
}
CLI usage (sanity checks)
git-insight-mcp who-touched src/auth.ts
git-insight-mcp co-change src/auth.ts
git-insight-mcp branches
git-insight-mcp recent alice
git-insight-mcp commit a3e577e
git-insight-mcp intro-pr src/auth.ts:42
git-insight-mcp intro-pr a3e577e
git-insight-mcp # MCP stdio server
Build from source
git clone https://github.com/HasanJahidul/git-insight-mcp.git
cd git-insight-mcp
npm install
npm run build
node dist/cli.js branches
Limits (v0.1)
- GitHub only (no GitLab/Bitbucket yet).
co_changeis O(window × files-per-commit) — defaults capped at 1000 commits.- Function-level blame is by line range, not AST. Renames not yet tracked.
- GH API rate limit applies (5000/h authed). PR results uncached this version.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.