Release Notes Server

What is Release Notes Server?

Release Notes Server is an MCP server that generates beautiful release notes from GitHub repositories. It fetches commits, organizes them by type (features, fixes, etc.), and presents them in a clean, readable Markdown format with emojis and statistics. It is designed for developers and teams who need to produce structured release summaries from GitHub projects.

How to use Release Notes Server?

Install the package via npm install and build it with npm run build. Add the server to your MCP configuration by specifying the node command pointing to the built index.js and providing a GITHUB_TOKEN environment variable for repository access. Invoke the generate_release_notes tool with parameters for owner, repo name, commit range (optional from/to SHA), and format options (type, grouping, statistics).

Key features of Release Notes Server

• Smart commit filtering by date or SHA
• Groups commits by type (features, fixes, documentation, etc.)
• Enriches commits with Pull Request data when available
• Includes detailed statistics (total commits, breaking changes, authors)
• Clean Markdown formatting with emojis and sections
• Efficient API usage using GitHub’s since parameter

Use cases of Release Notes Server

• Automatically generate release notes between two specific commits
• Produce a summary of changes for a new software release
• Display commit contributions grouped by type for a repository
• Generate statistics for weekly or monthly development reports
• Integrate release note generation into CI/CD pipelines

FAQ from Release Notes Server

What authentication is required to use Release Notes Server?

A GitHub personal access token with repository access must be provided via the GITHUB_TOKEN environment variable.

What output format does the server produce?

The release notes are generated in Markdown format, with sections for each commit type (e.g., 🚀 Features, 🐛 Fixes) and optional statistics.

How does the server filter commits?

Commits are filtered by a date range or by commit SHA using GitHub’s since parameter when possible, with fallback to SHA-based filtering as needed.

What parameters does the generate_release_notes tool accept?

It accepts owner, repo, a commitRange object with optional fromCommit and toCommit strings, and a format object specifying output type (markdown), grouping method (type), and whether to include statistics.

Are there any known performance limits?

The server handles pagination efficiently and maintains newest-first ordering, but no specific rate limits or runtime constraints are documented in the README.