Command Palette

Search for a command to run...

UnylyUnyly
Browse all

Git File Forensics

FreeNot checked

Provides deep git file-level forensics capabilities for tracking versions, analyzing diffs, examining commit contexts, and evaluating semantic changes in indivi

GitHubEmbed

About

Provides deep git file-level forensics capabilities for tracking versions, analyzing diffs, examining commit contexts, and evaluating semantic changes in individual files.

README

An MCP tool for deep git file-level forensics that helps get detailed insights into file histories, changes, and patterns, focusing on individual file analysis rather than repository-wide operations.

Installation

  1. Clone and build the server:
git clone [repository-url]
cd git-file-forensics
npm install
npm run build
  1. Add to your MCP settings (~/Library/Application Support/Code/User/globalStorage/david-dafu-dev.dafu/settings/cline_mcp_settings.json):
{
  "mcpServers": {
    "git-file-forensics": {
      "command": "/opt/homebrew/bin/node",
      "args": ["/path/to/git-file-forensics/build/index.js"],
      "alwaysAllow": []
    }
  }
}

Available Tools

1. track_file_versions

Tracks complete version history of a specific file, including renames and moves.

{
  "method": "tools/call",
  "params": {
    "name": "track_file_versions",
    "arguments": {
      "repoPath": "/path/to/repo",
      "file": "path/to/file",
      "outputPath": "output.json"
    }
  }
}

2. analyze_file_diff

Analyzes specific changes between any two versions of a file.

{
  "method": "tools/call",
  "params": {
    "name": "analyze_file_diff",
    "arguments": {
      "repoPath": "/path/to/repo",
      "file": "path/to/file",
      "versions": {
        "from": "commit-hash-1",
        "to": "commit-hash-2"
      },
      "outputPath": "output.json"
    }
  }
}

3. analyze_file_context

Analyzes broader context of file changes in a specific commit.

{
  "method": "tools/call",
  "params": {
    "name": "analyze_file_context",
    "arguments": {
      "repoPath": "/path/to/repo",
      "file": "path/to/file",
      "commit": "commit-hash",
      "outputPath": "output.json"
    }
  }
}

4. analyze_file_semantics

Analyzes semantic changes and patterns in file history.

{
  "method": "tools/call",
  "params": {
    "name": "analyze_file_semantics",
    "arguments": {
      "repoPath": "/path/to/repo",
      "file": "path/to/file",
      "outputPath": "output.json"
    }
  }
}

Output Format

All tools output JSON files containing:

  • Detailed analysis results
  • Summary statistics
  • Change patterns and relationships
  • Risk assessments (where applicable)

Requirements

  • Node.js
  • Git (must be installed and accessible)
  • MCP SDK

License

This project is licensed under the Apache License, Version 2.0 - see the LICENSE.txt file for details.

Copyright davidorex.ai. Licensed under the Apache License, Version 2.0; you may not use this project except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

from github.com/davidorex/git-file-forensics

Installing Git File Forensics

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/davidorex/git-file-forensics

FAQ

Is Git File Forensics MCP free?

Yes, Git File Forensics MCP is free — one-click install via Unyly at no cost.

Does Git File Forensics need an API key?

No, Git File Forensics runs without API keys or environment variables.

Is Git File Forensics hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install Git File Forensics in Claude Desktop, Claude Code or Cursor?

Open Git File Forensics on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare Git File Forensics with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All development MCPs