Release Notes Studio logo

Release Notes Studio

by info.sontusUpdated May 4, 2026

Converts pasted conventional commit messages into Keep a Changelog format, GitHub release notes, and marketing copy. Operates via paste-only input with no API keys required. Developers and project maintainers use it to generate structured release artifacts directly from git commit histories.

changelog
release-notes
conventional-commits
|

Overview

Release Notes Studio is an MCP server that processes conventional commit messages pasted by users to produce formatted outputs: Keep a Changelog entries, GitHub release note drafts, and marketing copy. It requires no API keys or external integrations, relying solely on user-provided commit text input.

Key Capabilities

  • Conventional commits to Keep a Changelog: Parses commit messages following the conventional commits spec (e.g., feat:, fix:, chore:) and organizes them into semantic changelog sections like Added, Changed, Fixed.
  • GitHub Release generation: Formats output as ready-to-paste GitHub release body text, including version headers and categorized changes.
  • Marketing copy: Generates promotional blurbs summarizing key features and fixes for announcements or blogs.

All functions use simple paste input of git log output, such as git log --oneline v1.0.0..HEAD.

Use Cases

  1. Open-source maintainer: Paste git log --pretty=format:'%s (%h)' v2.0.0..HEAD to get a Keep a Changelog section for the next release.
  2. Team lead preparing GitHub release: Input recent commits to produce formatted release notes for direct copy-paste into GitHub UI.
  3. Product manager: Generate marketing copy from commits to highlight new features in newsletters or social posts.
  4. CI/CD pipeline documentation: Manually paste build logs post-merge to create changelog updates without scripting.

Who This Is For

Software developers, open-source maintainers, DevOps engineers, and technical writers who manage git repositories and need quick, accurate release documentation from conventional commit histories. Suited for solo projects or teams avoiding complex automation setups.