analyze_commits
Analyze commits and provide statistics
LABSCO SUMMARY
The grouping is the product; the commit fetching is done carefully underneath.
Anyone can list commits — the value is that they come back sorted into features, fixes and the rest with authorship stats attached, ready to paste into a release. It uses GitHub's since parameter to cut API calls where it can and falls back to SHA filtering otherwise, which matters on repositories with long histories.
What it is
A server that reads a repository's commits over a range you specify, groups them by conventional-commit type, enriches them with pull request data where available, and returns formatted markdown.
What you get
- Release notes generated for an owner and repo over a commit range you give as
fromCommitandtoCommit—generate_release_notes - Commits grouped into sections: features, fixes, documentation, performance, refactoring, tests, build and other
- Optional statistics — total commits, breaking changes, and breakdowns by type and by author — controlled with
includeStats - Commits enriched with their pull request data when one exists, and newest-first ordering throughout
Requirements
A GitHub personal access token with repo access, in GITHUB_TOKEN. Node dependencies installed and built; the client runs build/index.js. The package is release-notes-server 0.1.0.
Setup effort
Build from source — git clone https://github.com/nickbaumann98/release-notes-server
USE CASES
01
Writing the release notes for a version you are about to ship
Give the previous release's SHA as the starting point and get the changes since then already grouped by type, with breaking changes called out.
02
Summarising a sprint for people who do not read commits
Generate notes over the sprint's commit range with statistics on, so the summary carries counts by type and by author alongside the prose.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
configure_template
Configure a custom template for release notes
generate_release_notes
Generate release notes from commits in a given timeframe or commit range
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. analyze_commits and configure_template are undocumented; only generate_release_notes is described.
Requires
GITHUB_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/nickbaumann98/release-notes-server
cd release-notes-server
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"release-notes": {
"command": "node",
"args": [
"<YOUR_PATH_TO_RELEASE_NOTES_SERVER>/build/index.js"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}
