Generate a changelog and release notes from git commit messages ($0.020)
generate_changelog_from_commitsTurn git commit messages (one per line, e.g. git log --oneline, or a JSON array of messages / GitHub commit objects) into a Keep a Changelog section, GitHub release notes (breaking changes first, contributors, compare link), the semver bump and next version from the previous one, and a launch post that fits X. Reads Conventional Commits, gitmoji and plain subjects; docs, tests, CI, dependency bumps and merges are counted, not listed. Deterministic, no AI, nothing stored. PAID: $0.020 per call in USDC on Base via x402 over MCP, or from prepaid credits if this server is configured with an Authorization: Bearer tkc_... header (see payment_options).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"commits": "<commits>"
},
"name": "generate_changelog_from_commits"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Release date YYYY-MM-DD (default: today, UTC, when there is a version) | |
| name | No | Product name for the launch post (default: the repo name), max 60 characters | |
| repo | No | GitHub owner/name (or URL) to link #refs, commits and the compare view | |
| commits | Yes | Commit messages, one per line (URL-encoded; indented lines and "BREAKING CHANGE:" footers attach to the commit above; an optional leading short SHA is kept), or a JSON array of strings or commit objects ({sha, message} or GitHub's {sha, commit: {message}, author: {login}}) | |
| version | No | Version of this release, e.g. 1.5.0 (default: the suggested next version when previous is given, else "Unreleased") | |
| previous | No | Previous released version, e.g. v1.4.2: gives the suggested next version and the compare link |