
Changelogforge
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Render a release changelog from merged pull requests, grouped by label, in Markdown.
Overview
Changelogforge's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Changelogforge 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
changelogforge
A release is ready, the pull requests are merged, and now someone has to turn that list into the changelog section readers will actually scan. changelogforge does that one job: it takes the merged pull requests for a release, sorts them into labelled groups, and renders the section as Markdown in a fixed, predictable shape.
- Grouping by label — each pull request joins the first
label in
group_orderthat it carries. The default order isfeature,bugfix,documentation,maintenance, and you can supply your own list to rename, reorder, add, or drop groups. Matching is exact and case-sensitive. - An other group — a pull request carrying none of the
group labels lands in a final group whose heading is
Other changes. Groups that end up empty are left out entirely, and the other group only appears when it has something in it. - Stable ordering — groups follow
group_orderwith the other group always last, and inside a group the pull requests are sorted by number ascending, so the same input always renders the same section. - Exact Markdown — the version heading sits at
heading_level(default 2) and group headings one level deeper. The result also returns the grouped structure itself, so a caller can render the same data another way.
Version and date are printed in the heading exactly as
given; neither is parsed or reformatted. Pull request
numbers must be unique across the list — a repeat is a
validation error naming both occurrences, for example
pull_requests[2].number duplicates pull_requests[0].number
— and every other malformed field is likewise an error
naming its path, with no partial section produced. The
computation is pure and local: no network, no
configuration, no files read beyond the input you pass in.
CLI
args.json contains the full arguments object:
labels defaults to [] per pull request, group_order
to ["feature", "bugfix", "documentation", "maintenance"],
and heading_level to 2. The rendered section is printed
as JSON:
Exit codes: 0 on success, 1 on a runtime error (including
an unreadable or invalid input file, or invalid input), 2
on a usage error.
MCP server
MCP client config:
Tools
-
generate_changelog— Render a release changelog section from merged pull requests, grouped by label.version(string, required) — release version label, printed verbatim in the headingdate(string, required) — release date, printed verbatim in the headingpull_requests(array, required, at least one) — merged pull requests as{number, title, labels?}objects;numberis unique across the listgroup_order(array of strings, optional) — labels that define groups, in output orderheading_level(integer, optional, 1–5) — Markdown heading level for the version heading
Returns
{version, date, groups, markdown, total_pull_requests}.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit 27adce7
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% 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