Release Notes Forge Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Summarize local Git release shape without returning commit messages, paths, hashes, or remotes.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that summarizes the shape of a Git repository's release history without exposing commit messages, paths, hashes, or remotes.

What you can do
  • Summarize the release shape of a local Git repository, such as how commits and releases are distributed over time.
  • Produce aggregate release summaries while withholding commit messages, file paths, commit hashes, and remote URLs.
  • Give an assistant a privacy-preserving view of repository history for drafting release notes or reporting on cadence.
When to use it
Use it when you want an assistant to describe a repository's release rhythm or history at a high level without handing over raw commit content, paths, or remote details. Useful for release-note drafting or reporting where source details should stay private.
Requirements
Runs as a local process over stdio, installed from the npm package release-notes-forge-mcp, so a Node.js runtime is needed. It works on local Git repositories on the user's machine; no authentication, environment variables, or headers are declared.
Before you install
It reads local Git repository data, so point it only at repositories you are comfortable having inspected. The manifest declares no credentials, but the tool list is not published, so verify what it actually reads and returns before relying on its privacy claims.

Installation

In SourceWeft

  1. Open Release Notes Forge Mcp in the dashboard and add it to a workspace.
  2. 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

release-notes-forge-mcp

Release Notes Forge reads local Git history and turns it into a release shape: commit count, broad change categories, and age buckets.

Quick start

bash
npm installnpm testnpm start

Use summarize_release_history with a local repository path inside RELEASE_NOTES_ROOT. The server never pushes, edits, or contacts a remote repository.

Privacy and limits

Commit messages, hashes, paths, branches, remotes, and author identities are suppressed. This is an aggregate release planning aid, not a changelog generator.

Source: README.md at commit 6b3fca4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 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.