Git Insights

io.github.basitalisandhuv0.1.1Updated Oct 5, 2026

Read-only git statistics for a local repository: log, blame ownership, churn, authors, large files.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Read-only git statistics for a local repository: log, blame ownership, churn, authors and large files.

What it does
Exposes read-only git statistics for a repository you name. Tools include repo_summary (branch, HEAD, remotes with credentials stripped, counts), git_log (commits with hash, author, date, subject and optional files), blame_summary (lines and latest commit per author for one file), churn (files ranked by commits with lines added and removed), authors (commits per email with first and last dates) and large_files (largest blobs in a tree or across history). Commands run without a shell from a fixed argument list, with validated paths and revisions, a 20 s timeout and an output cap.
When to use it
Useful when you want an assistant to inspect a local repository's history and ownership without changing it: reviewing who wrote which lines, finding churn hotspots, or seeing what makes a clone large.
Requirements
Local process over stdio; requires git on PATH. Install via npx (pin the version) or run the container image with docker. No accounts, API keys or environment variables are declared.
Before you install
It does not restrict which repository paths may be read, so run it under an account that should be able to read them. It is read-only: nothing is written, fetched or checked out, and no network access is used. Remotes are reported with credentials stripped from URLs.

Installation

In SourceWeft

  1. Open Git Insights in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

git-insights MCP server

Read-only statistics for a local git repository: log, blame ownership, churn, authors and large files. Every command is spawned without a shell from a fixed argument list, with validated paths and revisions, a 20 s timeout, an output cap and GIT_OPTIONAL_LOCKS=0. Nothing is written, fetched or checked out.

Part of dev-mcp-servers. Stdio transport only; the server never opens a port.

Tools

ToolInputWhat it returns
repo_summaryrepoTop level, branch, HEAD commit, remotes (credentials stripped from URLs), commit, tag and branch counts, modified and untracked file counts.
git_logrepo, rev?, limit? (1 to 500), path?, author?, since?, until?, grep?, no_merges?, with_files?Commits newest first with hash, author, ISO date, subject and optionally the files touched.
blame_summaryrepo, path, rev?, ignore_whitespace?Lines, percentage and latest commit per author for one file.
churnrepo, rev?, since?, until?, path?, limit?, max_commits?Files ranked by commits touching them with lines added and removed; renames are followed to the current name.
authorsrepo, rev?, since?, until?, path?, include_merges?, limit?Commits per author (by email) with first and last commit dates.
large_filesrepo, rev?, limit?, include_history?Largest blobs in a tree, or across all history (what makes a clone big).

Install

Claude Code:

bash
claude mcp add git-insights -- npx -y @basitalisandhu/[email protected]

Add -s user to make it available in every project. Any client that reads .mcp.json (Claude Code, Claude Desktop, Cursor):

json
{  "mcpServers": {    "git-insights": {      "command": "npx",      "args": ["-y", "@basitalisandhu/[email protected]"]    }  }}

Pin the version as shown so that an update to the package cannot change what runs in your editor without you noticing. From a checkout, use "command": "node", "args": ["<path>/packages/git-insights/dist/index.js"] after npm install && npm run build at the repository root.

What it touches

  • Network: None. git is run with GIT_TERMINAL_PROMPT=0; no command that contacts a remote is on the allowlist.
  • Local files: Runs git rev-parse, log, blame, ls-tree, rev-list, cat-file, status, remote, tag and branch in the repository you name. Revisions must match [A-Za-z0-9._/^~-] without ..; paths must be relative without ..; free-text filters may not start with -.
  • Telemetry: none.

Notes

  • The server does not restrict which repository paths may be read; run it under an account that should be able to read them.
  • Requires git on PATH.

Build and test

bash
npm install        # at the repository rootnpm run build -w @basitalisandhu/mcp-git-insightsnpm test -w @basitalisandhu/mcp-git-insights

Tests use node:test and the SDK's in-memory transport; they do not reach the network.

Licence

MIT. See LICENSE.

Source: packages/git-insights/README.md at commit 58c8c95

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.1LatestOct 5, 2026