Log inSubmit server
Git Insight MCP logo

Git Insight MCP

by HasanJahidul

Semantic Git queries for ownership, introducing pull requests, co-changed files, branch hygiene, recent work, and commit context.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Git Insight MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "hasanjahidul-git-insight-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "git-insight-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 6 tools correctly (1mo ago).

Overview

HasanJahidul/git-insight-mcp MCP server exposes semantic Git queries over MCP for files, lines, commits, and branches. It runs against a local repository and can optionally use the GitHub API to connect commits with pull requests and issues. Reach for it when an agent needs code ownership, change history, branch status, standup context, or related-file evidence beyond basic git log output.

Use cases

  • Find the primary owners of a file or line range
  • Trace a line or commit back to its introducing pull request
  • Identify stale or unmerged branches
  • Summarize a contributor's recent Git activity
  • Find files that frequently change with a target file

Key features

  • Grouped blame with primary ownership
  • Introducing pull-request lookup
  • Co-change file suggestions
  • Branch ahead/behind and stale status
  • Recent-work summaries
  • Commit context with issue linkage

Tools6

What Git Insight MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 36d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · git-insight-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads40Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed6Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Git Insight MCP works

What HasanJahidul/git-insight-mcp MCP server does

HasanJahidul/git-insight-mcp MCP server gives an MCP-compatible client structured answers about repository history and branch state. Its queries operate on local Git data and cover authorship, commit relationships, branch hygiene, recent activity, and files that tend to change together.

The server is intended for questions such as who last worked on a region of a file, which commit introduced a line, which branches are stale or unmerged, and what a contributor changed during a time window. With a GitHub token, it can also associate commits with pull requests and related issues. Without that token, the local Git features remain available.

How it works

The project runs as a local stdio MCP server. An MCP client starts the git-insight-mcp executable, and the server reads the repository’s local history to answer tool requests. It is not limited to the most recent few commits: several tools derive results from blame data, commit windows, branch comparisons, and commit metadata.

For introducing pull requests, the server first examines merge-message information and can fall back to the GitHub API. GitHub access is limited to GitHub repositories; GitLab and Bitbucket are not supported. Pull-request results are not cached in the current version, so API rate limits apply. An authenticated GitHub API limit is documented as 5,000 requests per hour.

Setup and configuration

Install the package globally with npm:

Terminal
npm install -g git-insight-mcp

A Claude Code configuration can start it with:

Terminal
claude mcp add --scope user git-insight -- git-insight-mcp

Other MCP-compatible clients can launch the same executable as a stdio server. Set GH_TOKEN when pull-request or issue lookups are needed. The token is optional for local Git queries.

The repository can also be built from source by cloning it, running npm install, running npm run build, and invoking the resulting CLI under dist/cli.js.

Tools and capabilities

  • who_touched groups blame results by author and reports line counts, related commits, last-touch dates, and a primary owner. It accepts an optional line range.
  • introducing_pr looks for the pull request associated with a line or commit, using merge messages before consulting GitHub.
  • co_change finds files most frequently changed alongside a selected file.
  • branch_hygiene reports ahead and behind counts, the last commit, merged state, and whether branches are stale.
  • recent_work summarizes an author’s commits, files, and insertions or deletions over a selected period.
  • commit_context returns commit subject and body, changed files, pull-request information, and related issues.

The command-line interface also exposes sanity-check commands such as who-touched, co-change, branches, recent, commit, and intro-pr.

Limitations and notes

co_change can be expensive because its work scales with the commit window and the number of files per commit; the default history window is capped at 1,000 commits. Function-level ownership is approximated using line ranges rather than an AST, and renames are not tracked yet.

GitHub linkage requires the optional token and is subject to API limits. The current release supports GitHub only for remote repository metadata. HasanJahidul/git-insight-mcp MCP server is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Git Insight MCP

Install it globally with `npm install -g git-insight-mcp`, then start the `git-insight-mcp` executable as a stdio MCP server.

No. Local Git tools work without a token. Set `GH_TOKEN` to enable pull-request and issue lookups through GitHub.

GitHub is supported for pull-request and issue linkage. GitLab and Bitbucket are not supported in the current version.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGit Insight MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hasanjahidul-git-insight-mcp?style=directory)](https://allmcps.com/mcp/hasanjahidul-git-insight-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/hasanjahidul-git-insight-mcp"><img src="https://allmcps.com/api/badge/hasanjahidul-git-insight-mcp?style=directory" alt="Git Insight MCP on AllMCPs" /></a>