SuperAPI AI Directory

git-insight-mcp

Semantic git queries: blame grouped by author, introducing PR, co-change suggestions, branch hygiene, recent-work standups and full commit context.

Open website

About this tool

git-insight-mcp is a semantic Git query tool based on MCP (Model Context Protocol), designed to let LLM agents edit code more safely by answering questions that regular git log struggles to handle, thereby supplementing context. It can be used together with terminal-history-mcp and localhost-mcp to jointly cover "what you ran, what is running, and what you changed."

Main uses and capabilities:

  • Blame grouped by author: answer "Who last modified this function?" without inspecting line by line.
  • Find the introducing PR: answer "Which PR introduced this line?" and avoid manually going blame -> commit SHA -> search.
  • File co-change suggestions: discover "Which files always change together?".
  • Branch hygiene: view branches that have not been merged for more than 30 days.
  • Recent work summary: quickly review "What work did I do last week?".
  • Full commit context: provide semantic who/what/when/why information for any line, file, or branch.

How to use:

  • Connect to Claude Code or any MCP-compatible client and run it as a stdio MCP server.
  • For PR/issue queries, a GitHub token must be set; without a token the local git tools still work, but PR association will be skipped.
  • A sanity check can be performed via the CLI, and building from source is supported.

Applicable scenarios:

  • Developers quickly locating code history and ownership in daily work.
  • LLM agents obtaining the necessary Git context before making safe code edits.
  • Teams performing branch maintenance, work reviews, and code change analysis.

Limitations:

  • Currently only GitHub is supported; GitLab/Bitbucket are not yet supported.
  • co_change complexity is O(window x files-per-commit), with a default limit of 1000 commits.
  • Function-level blame is based on line ranges rather than an AST, and renames are not yet tracked.
  • The GitHub API has rate limits (5000/hour after authentication).
  • In this version, PR results are not cached.