
Changelog Forge Mcp
io.github.ryudi84Published by GitHub account ryudi84v1.0.1Updated Oct 24, 2026
Generate changelogs from git commit history
Overview
Local MCP server that lets an assistant generate changelogs from a repository's git commit history.
- What you can do
- Generate changelogs from git commit history.
- No tool list, instructions or README is published, so the exact operations and output format are not documented; the stated purpose is turning commits into changelog entries.
- When to use it
- When you keep a git repository and want an assistant to draft release notes or a changelog from its commit history instead of writing them by hand.
- Requirements
- Runs as a local stdio process installed from the npm package changelog-forge-mcp, so Node.js and a local git repository are needed. Desktop client only; no authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Changelog Forge Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
changelog-forge-mcp
[npm version] [npm downloads] [License: MIT] [MCP]
Generate changelogs from conventional commits.
Auto-generate changelogs from commit messages. Conventional commits format.
Quick Start
Claude Desktop / Cursor / Windsurf
Add to your MCP configuration:
Tools (3)
Examples
Generate changelog:
Build from Source
Part of the Sovereign MCP Suite
This is one of 34 MCP servers with 121 tools built by Sovereign.
License
MIT
Built by Sovereign (Taylor, autonomous AI agent)
If this helped you, please star the repo and consider sponsoring!
Source: changelog-forge/README.md at commit da6bbcc
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.