Git MCP Server Development Manager Analytics Tools
This MCP server enables development managers to analyze Git repositories without writing any code. Simply ask Claude questions about your project, and get detailed analytics about commits, developers, code changes, and team performance.
Installation
npx git-mcp-server---development-manager-analytics-toolsAsk AI about Git MCP Server Development Manager Analytics Tools
Powered by Claude Β· Grounded in docs
I know everything about Git MCP Server Development Manager Analytics Tools. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
Git MCP Server - Development Manager Analytics Tools
A Model Context Protocol (MCP) server providing Git repository analysis tools designed specifically for development managers. Get instant insights into team performance, code health, and project trends through natural language conversations with Claude.
Overview
This MCP server enables development managers to analyze Git repositories without writing any code. Simply ask Claude questions about your project, and get detailed analytics about commits, developers, code changes, and team performance.
Perfect for managers who want to:
- Track team productivity and individual contributions
- Identify bottlenecks and inactive developers
- Monitor project health and code quality trends
- Generate weekly/monthly progress reports
- Make data-driven decisions with insights into team performance and workload distribution
π₯ Live Demo
Want to see it in action first?
- π Full Documentation & Demo - Complete guide with visual examples and video walkthrough
- π Interactive Dashboard - Live executive dashboard with charts and metrics
- π¬ Example Conversation - Real analysis of the ONNX Runtime project
See how development managers use this tool to track team performance, identify key contributors, and generate actionable insights.
Features
7 Powerful Analytics Tools
- Project Dashboard - Comprehensive overview of repository activity
- Commit History - Detailed commit analysis with file changes and statistics
- Developer Statistics - Individual developer performance metrics
- Developer Comparison - Side-by-side comparison of team members
- File Change Tracking - Monitor changes to critical files over time
- Branch Management - Track all branches and their activity
- Repository Sync - Keep your local repository up to date
Key Capabilities
- Time-based filtering - Analyze any time period (last week, last month, custom ranges)
- Developer-specific insights - Track individual contributions and patterns
- Code quality indicators - Commit sizes, code churn, collaboration patterns
- Trend analysis - Compare activity across different time periods
- Natural language interface - No Git commands needed, just ask Claude
5 Ready-to-Use Prompts
Pre-configured questions for common management tasks - no typing needed, just select and go:
- π Executive Dashboard - Visual overview with charts for last 7 days (includes week-over-week comparison)
- π Code Review Priority - Files that changed most in last 7 days
- π€ Developer Spotlight - Individual contributions and impact (30 days)
- πΏ Active Branches - Track ongoing work (30 days)
- β‘ Quick Daily Sync - Today's activity summary
These prompts automatically request visual charts for easy-to-understand insights.
Installation
Prerequisites
- Python 3.8 or higher
- Git installed and accessible in PATH
- Claude Desktop or compatible MCP client
Setup
-
Clone the repository
git clone https://github.com/naomiOvad/Git-MCP-Server---Development-Manager-Analytics-Tools gitMCP cd gitMCP -
Install dependencies
pip install -r requirements.txt -
Configure Claude Desktop
Add to your Claude Desktop configuration file:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:~/Library/Application Support/Claude/claude_desktop_config.json{ "mcpServers": { "git-mcp": { "command": "python", "args": ["C:\\path\\to\\gitMCP\\server.py"] } } } -
Restart Claude Desktop
The MCP server will automatically start when you launch Claude Desktop.
Usage
Quick Start
Once configured, simply start a conversation with Claude and provide your repository path:
Hello! I'm a development manager for the ONNX Runtime project
(C:\Projects\onnxruntime). I'd like to understand the team's activity
over the last 30 days.
Claude will use the MCP tools to analyze your repository and provide detailed insights.
Example Questions
Weekly Progress Reports:
Give me a weekly progress report comparing last week vs. this week.
How many commits, developers, and lines of code changed?
Team Performance:
Who are the top 10 most active developers this month?
Show me their commit counts and code contributions.
Individual Analysis:
Give me a detailed report on developer@example.com:
- How many commits in the last 30 days?
- What files did they work on?
- What was her contribution, and how did it impact the project?
Trend Analysis:
Compare activity across the last 3 months. Is the team becoming
more or less productive? Show me the numbers.
Branch Management:
Which branches has john.doe@company.com worked on recently?
Show me his commits and the names of the branches he worked on.
Developer Comparison:
Compare these 3 developers and their work styles. Who focuses on
what areas? How do their contributions differ?
Available Tools
1. get_project_dashboard
Purpose: Comprehensive project overview Parameters:
repo_path(required): Absolute path to repositorysince: Start date (default: "30 days ago")until: End date (optional)
Returns: Complete dashboard with commit stats, top contributors, active areas, and summary metrics
2. get_commit_history
Purpose: Detailed commit history with file changes Parameters:
repo_path(required): Absolute path to repositorybranch: Specific branch (default: all branches)max_count: Maximum commits to returnsince: Commits since dateuntil: Commits until dateauthor: Filter by author name/email
Returns: List of commits with file changes, additions/deletions, and summary statistics
3. get_developer_stats
Purpose: Individual developer performance metrics Parameters:
repo_path(required): Absolute path to repositoryauthor(required): Developer name or emailsince: Start dateuntil: End date
Returns: Developer's commit count, code contributions, files modified, and activity patterns
4. compare_developer_stats
Purpose: Side-by-side developer comparison Parameters:
repo_path(required): Absolute path to repositoryauthors(required): List of developer names/emailssince: Start dateuntil: End date
Returns: Comparative analysis of multiple developers' contributions and work patterns
5. get_file_changes
Purpose: Track changes to specific files Parameters:
repo_path(required): Absolute path to repositoryfile_path(required): Path to file relative to repo rootsince: Start dateuntil: End datemax_count: Maximum commits to show
Returns: Complete history of changes to a specific file, including who changed it and when
6. get_branch_list
Purpose: List all branches with activity Parameters:
repo_path(required): Absolute path to repository
Returns: All local and remote branches sorted by most recent activity
7. git_sync
Purpose: Sync repository with remote Parameters:
repo_path(required): Absolute path to repository
Returns: Status of fetch operation
Tool Workflows
Examples of how Claude sequences multiple tools to answer complex questions:
Weekly Team Review
Question: "Compare each developer's performance this week vs last week and rank them"
Tool Sequence:
get_commit_history(both periods) β Gather commit dataget_developer_stats(multiple developers) β Individual metricscompare_developer_statsβ Ranking and comparison
Code Review Prioritization
Question: "What files need urgent code review?"
Tool Sequence:
get_project_dashboardβ Identify hotspot filesget_commit_historyβ Detailed change analysis- Response prioritizes files by activity and risk
Developer Performance Analysis
Question: "Show me john.doe@company.com performance, compare to team, and list his recent commits"
Tool Sequence:
get_developer_stats(target developer) β Individual metricscompare_developer_stats(all developers) β Team comparisonget_commit_history(filtered by developer) β Recent work
These workflows show how the server intelligently combines tools to provide comprehensive answers.
Technical Details
Architecture
gitMCP/
βββ server.py # MCP server entry point
βββ prompts.py # Pre-configured prompts
βββ git_runner.py # Git command execution
βββ exceptions.py # Custom error handling
βββ requirements.txt # Dependencies
βββ tools/ # MCP tool implementations
β βββ git_dashboard.py
β βββ git_commit_history.py
β βββ git_developer_stats.py
β βββ git_compare_developers.py
β βββ git_file_changes.py
β βββ git_branches.py
β βββ git_sync.py
βββ tests/ # Test suite
βββ conftest.py
βββ test_*.py
Error Handling
The server includes custom exception handling for common Git operations:
- GitNotFoundError - Git executable not found in PATH
- GitRepositoryError - Invalid or non-existent repository
- GitCommandError - Git command execution failure
- GitTimeoutError - Command timeout (default: 60 seconds)
Type Safety
All functions include comprehensive type hints for better IDE support and code quality:
- Input validation
- Return type annotations
- Optional parameter handling
Testing
Run Tests
# Run all tests
pytest
# Run with coverage
pytest --cov=. --cov-report=html
# Run specific test file
pytest tests/test_commit_history.py
Configure Test Repository
Set your test repository via environment variable:
# Windows
set TEST_REPO_PATH=C:\path\to\your\test\repo
# Linux/Mac
export TEST_REPO_PATH=/path/to/your/test/repo
Or modify tests/conftest.py to set a default path.
Use Cases
For Development Managers
- Weekly Standups - Generate team activity summaries
- Performance Reviews - Track individual contributions over time
- Project Planning - Identify active areas and inform resource decisions
- Team Health - Detect inactive developers and potential issues
- Sprint Reviews - Compare velocity across sprints
For Technical Leads
- Code Review Prioritization - Identify large changes needing review
- Bus Factor Analysis - Find single points of failure
- Onboarding - Track new developer integration
- Quality Metrics - Monitor code churn and commit patterns
Author
Created by Naomi Ovadia (n0583267045@gmail.com)
Developed as a professional tool for development managers to gain insights into team performance and project health through natural language interactions with Claude.
Built with:
- FastMCP - Model Context Protocol framework
- Python 3.8+
- Git
Tested on: ONNX Runtime - Microsoft's open-source project with 870+ contributors
