About Git Forensics MCP
Git Forensics MCP is an MCP server for investigating Git repositories, aimed at teams examining branch relationships, development activity, and change risks. It focuses on repository analysis rather than general GitHub or Git operations.
Key features
- 01Branch state and relationship overview
- 02Commit activity by time period
- 03File change tracking across branches
- 04Conflict risk assessment and merge guidance
- 05Write analysis results as JSON files
Use cases
- 01Review branch states and merge bases
- 02Examine development activity in a period
- 03Identify file hotspots and conflict risks
MCP support
The MCP server provides repository analysis tools to compatible clients over stdio. Analysis results are written as JSON files at a specified path.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEGit Forensics MCP
A specialized Model Context Protocol (MCP) server for deep git repository investigation and analysis. This forensics tool provides detailed insights into repository history, branch relationships, and development patterns, focusing solely on git repository analysis rather than general GitHub or git operations.
Features
The server provides four main analysis tools:
-
Branch Overview (
get_branch_overview)- Provides high-level overview of branch states and relationships
- Analyzes last commits, commit counts, and merge bases
- Generates statistical summaries of branch activities
-
Time Period Analysis (
analyze_time_period)- Analyzes detailed development activity in specific time periods
- Categorizes commits (feature, fix, refactor, docs, other)
- Provides activity summaries with commit patterns
-
File Changes Analysis (
analyze_file_changes)- Tracks changes to specific files across branches
- Identifies potential conflict areas
- Provides risk assessment for file modifications
- Generates recommended review order based on risk levels
-
Merge Recommendations (
get_merge_recommendations)- Determines optimal merge strategies
- Assesses conflict risks
- Identifies code hotspots
- Provides step-by-step merge guidance
Input Parameters
Each tool requires specific parameters:
repoPath: Path to the git repositorybranches: Array of branch names to analyzeoutputPath: Path where analysis results will be written- Additional tool-specific parameters:
timeRange: Start and end dates for period analysisfiles: Array of file paths for file change analysis
Output Format
All tools output JSON files containing:
- Detailed analysis results
- Summary statistics
- Risk assessments (where applicable)
- Recommendations based on analysis
Technical Details
- Built with TypeScript
- Uses MCP SDK for server implementation
- Executes git commands through child processes
- Provides error handling and validation
- Runs on stdio transport
Dependencies
- @modelcontextprotocol/sdk
- Node.js
- Git (must be installed and accessible)
Usage
The server runs as an MCP service and can be integrated with any MCP-compatible client. All analysis results are written to specified output files in JSON format.
Contributing and License
This project is licensed under the Apache License, Version 2.0 - see the LICENSE.txt file for details.
Collaboration Welcome
Forks and contributions welcome.
All contributions will be under the Apache License 2.0. This permissive license allows you to:
- Use the code commercially
- Modify and distribute the code
- Create derivative works
- Include in other projects
Copyright 2025. 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.