get_repository_overviewLABSCO SUMMARY
Repository questions that git log makes tedious.
It answers the maintenance questions — who owns this area, which files never stop changing, whether a branch has drifted — from the repository itself, so the answer is current rather than remembered.
What it is
Eight read-only analytics calls over a local Git repository: totals, contributors, branches, files, commit timeline, commit frequency, and lines added versus removed.
What you get
- A summary of the repository with key metrics and top contributors
- Detailed statistics: commits, authors, branches, span of history
- A contributor breakdown with commit patterns and activity periods
- Branch health, including ahead and behind status
- The files modified most often, and who modifies them
- A commit timeline you can filter
- Daily commit frequency over a period
- Lines added and removed over time
Requirements
Node.js 18 or newer, a checkout of the repository you want analysed, and a build step — install dependencies and build before pointing your client at the compiled server.
Setup effort
Build from source — git clone https://github.com/singhashish4000/MCP-Server.git
USE CASES
01
Sizing up a codebase you just inherited
One call gives the shape of the project and who has been in it, before you start reading files.
02
Finding who to ask about a file
The file's modification history and the contributors behind it, instead of guessing from the last commit.
03
Spotting code that never settles
Lines added and removed over time, cross-read with the files that change most — the pair that identifies a hotspot.
04
Checking whether a branch has drifted
Ahead and behind counts with recent activity, so a merge decision is made on numbers.
05
Writing up what changed this quarter
A filtered commit timeline plus daily frequency, which is most of a release note before you write a word.
8 tools
Listed in project docs. Your client may show a different list.
get_repository_statsget_author_statsget_branch_statsget_file_statsget_commit_historyget_commit_frequencyget_code_churnBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
Node.js 18+
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/singhashish4000/MCP-Server.git
cd MCP-Server
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"git-analytics": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SERVER>/dist/index.js"
]
}
}
}
