Gi MCP Server

@HasanJahidul

リポジトリ

基本情報

カテゴリ

バージョン管理

トランスポート

stdio

作者

HasanJahidul

投稿者

Jahidul Hasan

Gi MCP Server について

概要はまだありません

#git#blame#co-change#github #pull-request#branch-hygiene#code-ownership#developer-tools #mcp-server

Gi MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "git-insight": {
      "command": "git-insight-mcp"
    }
  }
}

Gi MCP Server のツール

Group blame by author. Lines, commits, last-touched, primary owner. Optional line-range narrowing.

Find the PR that introduced a line (or commit). Parses merge messages first; falls back to GitHub API.

Files most often changed together with the input file.

List branches with ahead/behind, last commit, merged status, stale flag.

Standup helper: author's commits + files + ins/del in a window.

Full commit context: subject, body, files, PR, related issues.

概要

What is git-insight-mcp?

git‑insight‑mcp is an MCP server that enables semantic git queries — answering who, what, when, and why about any line, file, or branch. It integrates with any local git repository and is designed for developers and LLM agents who need richer git context than git log provides.

How to use git-insight-mcp?

Install globally via npm install -g git-insight-mcp, then wire it into an MCP‑compatible client (e.g., Claude Code with claude mcp add --scope user git-insight -- git-insight-mcp). It runs as a stdio MCP server. For PR and issue lookups, set the environment variable GH_TOKEN. Use the provided CLI commands (e.g., git-insight-mcp who-touched src/auth.ts) for ad‑hoc checks.

Key features of git-insight-mcp

who_touched – Group blame by author, lines, commits, and primary owner.
introducing_pr – Find the PR that introduced a line or commit.
co_change – Identify files most often changed together with a given file.
branch_hygiene – List branches with ahead/behind, last commit, merged status, and stale flag.
recent_work – Standup helper: author’s commits, files, and insertion/deletion counts.
commit_context – Full commit details including subject, body, files, PR, and related issues.

Use cases of git-insight-mcp

Determine who last touched a function or code region.
Find which PR introduced a specific line of code.
Identify files that frequently change together to plan refactors.
List stale or unmerged branches for cleanup.
Generate a summary of recent work for standups or reports.

よくある質問

What dependencies does git-insight-mcp require?

Node.js (npm) and a local git repository. An optional GitHub token (`GH_TOKEN`) enables PR/issue lookups; without it, local‑git tools still work.

Does git-insight-mcp support GitLab or Bitbucket?

No, only GitHub is supported. PR linkage falls back to the GitHub API.

How do I set up GitHub authentication for PR lookups?

Set the environment variable `GH_TOKEN` to a valid GitHub personal access token. Without a token, PR lookup is skipped but all other tools remain functional.

What are the performance limits?

The `co_change` tool is O(window × files‑per‑commit) with a default cap of 1000 commits. Function‑level blame is based on line ranges, not AST, and renames are not yet tracked. GitHub API rate limits apply (5000 requests per hour for authenticated users).