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 "Install 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-mcpGenerate 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: gitrama-mcp
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
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SiwarKhalfaoui/github-changelog-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server