Skip to main content
Glama
Git File Forensics MCP

Git File Forensics MCP

by davidorex

Git File Forensics MCP

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": []
    }
  }
}

Related MCP server: git-repo-analyzer-mcp

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

Available Tools

4 tools
analyze_file_contextC

Analyze broader context of file changes in a specific commit

Inputs: repoPath (required), file (required), commit (required), outputPath (required).

analyze_file_diffC

Analyze specific changes between any two versions of a file

Inputs: repoPath (required), file (required), versions (required), outputPath (required).

analyze_file_semanticsC

Analyze semantic changes and patterns in file history

Inputs: repoPath (required), file (required), outputPath (required).

track_file_versionsC

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

Inputs: repoPath (required), file (required), outputPath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: analyze_file_context focuses on broader changes in a commit, analyze_file_diff examines specific changes between versions, analyze_file_semantics looks at semantic patterns in history, and track_file_versions tracks complete version history including renames. There is no overlap or ambiguity between these tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'analyze' or 'track' as the verb and descriptive nouns like 'file_context', 'file_diff', 'file_semantics', and 'file_versions'. The naming is uniform and predictable throughout the set.

    Tool Count5/5

    With 4 tools, this server is well-scoped for its purpose of Git file forensics. Each tool earns its place by covering distinct aspects of file analysis and tracking, avoiding bloat while providing comprehensive coverage for the domain.

    Completeness5/5

    The tool set provides complete coverage for Git file forensics: analyzing context, diffs, semantics, and version tracking. There are no obvious gaps, as these tools cover the core lifecycle of file changes, renames, and historical patterns without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables analysis of local Git repositories via standard git commands, providing insights like line authorship, commit frequency, code churn, and co-changed files.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only, structured access to a Git repository's history through seven typed tools, enabling search commits, file evolution, blame, churn, contributors, commit details, and ref comparisons without a shell.
      MIT