github-changelog-mcp
Generates categorized changelogs from GitHub commit history between two refs, lists tags, and compares refs via the GitHub REST API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@github-changelog-mcp Generate changelog for tensorflow/tensorflow from v2.10 to v2.11"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
github-changelog-mcp
An MCP server that turns raw GitHub commit history into a categorized, human-readable changelog — directly inside Claude (or any MCP-compatible client).
You: "Generate a changelog for expressjs/express between v4.18.0 and v4.19.0"
Claude: [calls generate_changelog tool]
## expressjs/express: v4.18.0 → v4.19.0
### Features
- add support for X-Forwarded-Host header (`a1b2c3d`) — @wesleytodd
### Bug Fixes
- prevent ReDoS in query parser (`b2c3d4e`) — @cdoublev
### Chores
- bump path-to-regexp to 0.1.10 (`c3d4e5f`) — @dependabotNo paid APIs. No API keys required to get started (an optional free GitHub token just raises the rate limit).
Why this exists
Writing release notes by hand is tedious and usually done by skimming
git log and manually sorting commits into categories. This tool automates
that: it fetches the commit diff between two refs via GitHub's public REST
API, classifies each commit (Conventional Commits
prefix first, keyword heuristics as a fallback), filters out merge-commit
noise, and renders clean grouped Markdown — as a tool Claude can call
directly in conversation.
Related MCP server: mcp-github-pm
Tools
Tool | Description |
| List recent tags for a public repo (use this to find valid ref names) |
| Raw commit diff between two refs, uncategorized |
| The main tool — categorized Markdown changelog between two refs, with optional contributor summary |
Setup
git clone https://github.com/SiwarKhalfaoui/github-changelog-mcp.git
cd github-changelog-mcp
npm install
npm run buildOptional — raise the GitHub API rate limit from 60/hr to 5,000/hr:
cp .env.example .env
# add a free token from https://github.com/settings/tokens (no scopes needed)Connect it to Claude Desktop
Add this to your Claude Desktop config
(~/Library/Application Support/Claude/claude_desktop_config.json on macOS,
%APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"github-changelog": {
"command": "node",
"args": ["/absolute/path/to/github-changelog-mcp/build/index.js"],
"env": {
"GITHUB_TOKEN": "optional-token-here"
}
}
}
}Restart Claude Desktop. You should see a 🔨 tools icon confirming the server connected — then just ask Claude to generate a changelog for any public repo.
Development
npm run dev # run directly with tsx, no build step
npm run test:changelog # run the categorization logic test suiteArchitecture notes
src/github.ts— thin GitHub REST API wrapper. No SDK dependency, justfetch+ a shared header builder. Handles rate-limit errors explicitly and surfaces an actionable message (which token to add, when the limit resets) rather than a raw HTTP error.src/changelog.ts— the actual logic: Conventional Commits parsing with a keyword-based fallback for repos that don't use that convention, merge commit filtering, and Markdown rendering.src/index.ts— MCP server wiring (tool registration, schemas viazod, stdio transport).
Kept intentionally dependency-light — GitHub's REST API and MCP's official SDK are the only two runtime dependencies. No frameworks, no ORMs, no unnecessary abstraction for a tool this size.
Possible extensions
Group changelog entries by scope (
feat(auth): ...→ group under "Auth") in addition to typeCompare against unreleased commits (
to_ref= default branch) and suggest the next semver bump based on commit types presentCache
compareRefsresponses per (owner, repo, base, head) to reduce API calls on repeated queries in the same session
License
MIT
Available Tools
3 toolscompare_refsCompare two refsA
Show the raw commit diff between two Git refs (tags, branches, or SHAs) in a public GitHub repository, without categorization.
Inputs: base (required), head (required), repo (required), owner (required).
generate_changelogGenerate a categorized changelogA
Generate a clean, categorized Markdown changelog (Features / Bug Fixes / Docs / etc.) between two refs in a public GitHub repository. Uses Conventional Commits parsing where available and falls back to keyword heuristics otherwise. This is the main tool — use list_tags first if you don't know valid ref names.
Inputs: repo (required), owner (required), to_ref (required), from_ref (required), +1 more.
list_tagsList repository tagsA
List the most recent Git tags/releases for a public GitHub repository. Use this first to find valid ref names for generate_changelog.
Inputs: repo (required), owner (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing tags for reference, generating a categorized changelog, and showing a raw diff. There is no overlap or ambiguity.
All tool names follow a consistent snake_case verb_noun pattern (list_tags, compare_refs, generate_changelog), making them predictable and easy to remember.
Three tools is perfectly scoped for a changelog-focused server. Each tool serves a necessary step without bloat or deficiency.
The tool set covers the full workflow: listing available refs, generating a changelog, and providing a raw diff for verification. No obvious gaps for the declared purpose.
Maintenance
Related MCP Connectors
Generate changelogs, release emails, help-center articles, banners, and social posts from commits.
Turn a raw dev log (commit subjects, PR titles) into customer-facing release notes Markdown.
Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.
Release intelligence for AI coding tools: releases, typed changes, breaking changes, cadence.
Related MCP Servers
- FlicenseBqualityDmaintenanceGenerates comprehensive and formatted release notes from GitHub repositories, efficiently organizing commits by type and including detailed statistics using smart API usage.33-
- AlicenseBqualityDmaintenanceEnables GitHub project management from Claude, supporting issue creation, milestones, labels, changelog generation, and repository stats.85 npm1MIT
- AlicenseBqualityDmaintenanceEnables AI agents to read git commits from local repositories and generate beautifully formatted, categorized changelogs.23 npmMIT
- AlicenseNot gradedqualityDmaintenanceGenerate professional changelogs from git history and suggest semver bumps, with optional AI enhancement via Claude.42 npm2MIT