Release Intel

io.github.barissozudogruPublished by GitHub account barissozudogruv0.7.2Updated Oct 25, 2026

Correlates commits, PRs, issues and contributors between two git refs for release notes.

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

A local MCP server that compares two Git refs in a GitHub repository and assembles commits, merged pull requests, linked issues and contributors into a release-

What you can do
Compare two Git refs and return commits enriched with merged pull request metadata and linked issues, plus merged pull requests grouped into categories such as breaking, feature, fix, docs, chore, dependency, release or other, and a full release summary with aggregate statistics and contributors. Also ships a terminal command that produces a Markdown or JSON release report and a GitHub Action that writes the evidence report to a workflow summary.
When to use it
Useful when drafting release notes or changelogs for a GitHub repository and you want the assistant to gather the underlying evidence from a bounded ref range instead of working from a blank prompt. Also fits CI workflows that attach release evidence to a job summary before publishing.
Requirements
Runs locally via npx with Node.js 18 or newer, or in Docker. Needs a GitHub token with read-only repository access supplied in the GITHUB_TOKEN environment variable. Network access to the GitHub API is required. Optionally serves over HTTP on a local port.
Before you install
Requires a GitHub token; use a fine-grained, read-only token limited to the repositories you want inspected, since the server needs no write permission. The token stays in the local process and is sent only to the GitHub API. The server reads repository data and does not publish releases or modify content. Very large ref ranges may be truncated by GitHub's compare endpoint, and release categories are heuristics that still need review.

Installation

In SourceWeft

  1. Open Release Intel 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-intel-mcp]

[npm version] [npm downloads] [CI] [MCP Registry] [MIT license]

release-intel-mcp

Build release context from repository evidence instead of a blank prompt. The server compares two Git refs and correlates commits, merged pull requests, linked issues, labels, changed files, and contributors into a structured release record.

Tool page · npm · Listed in the official MCP Registry

Start in one minute

Create a fine-grained GitHub token with read-only access to the repositories you want to inspect. Repository contents and pull requests are sufficient for the current tools. No write permission is needed.

json
{  "mcpServers": {    "release-intel": {      "command": "npx",      "args": ["-y", "@barissozudogru/release-intel-mcp"],      "env": {        "GITHUB_TOKEN": "your_read_only_token"      }    }  }}

Then ask the client for a bounded range:

text
Use release-intel to build release evidence for owner/repositoryfrom v1.4.0 to v1.5.0. Separate merged PRs from direct commitsand preserve links to the repository record.

The token stays in the local server process and is sent only to the GitHub API.

Proof on this repository

A verified run against the stable range v0.5.1...8a2f350 returned:

text
Repository:        barissozudogru/release-intel-mcpCommits:           14Merged PRs:        1Files changed:     12Lines added:       286Lines deleted:     135Contributors:      1

The response also includes commit SHAs, messages, authors, pull request categories, linked issues, and warnings when GitHub truncates or fails part of the evidence lookup.

If this saves you time, consider starring the repository. It helps other developers find it.

Tools

ToolWhat it returns
get_changes_between_refsCommits enriched with merged pull request metadata and linked issues
get_pull_requests_in_rangeMerged pull requests grouped as breaking, feature, fix, docs, chore, dependency, release, or other
get_release_summaryA complete release evidence object with aggregate statistics and contributors

The categorization uses labels and conventional title signals. Repository labels, issue links, and pull request hygiene directly affect the result. The server provides evidence and structure; the final release narrative still needs review.

Release report command

The package includes a terminal command that produces Markdown by default:

bash
GITHUB_TOKEN=your_read_only_token \  npx --yes --package @barissozudogru/release-intel-mcp \  release-intel-report owner/repository v1.4.0 v1.5.0

Use --json when another tool will consume the report:

bash
release-intel-report owner/repository v1.4.0 v1.5.0 --json

GitHub Action

Attach the evidence report to the workflow summary before publishing a release:

yaml
name: Release evidence
on:  workflow_dispatch:    inputs:      from_ref:        required: true      to_ref:        required: true
jobs:  evidence:    runs-on: ubuntu-latest    permissions:      contents: read      pull-requests: read    steps:      - uses: barissozudogru/[email protected]        with:          from-ref: ${{ inputs.from_ref }}          to-ref: ${{ inputs.to_ref }}          token: ${{ secrets.GITHUB_TOKEN }}

This action reads repository data and writes Markdown to the job summary. It does not publish a release or modify repository content.

Client setup

Claude Desktop, Cursor, Windsurf, Cline, and similar clients

Use the stdio configuration from the quickstart. The server entry is identical across these clients even when their config file locations differ.

VS Code with Copilot

Create .vscode/mcp.json:

json
{  "servers": {    "release-intel": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@barissozudogru/release-intel-mcp"],      "env": {        "GITHUB_TOKEN": "your_read_only_token"      }    }  }}
Streamable HTTP
bash
GITHUB_TOKEN=your_read_only_token \  npx @barissozudogru/release-intel-mcp --http

The MCP endpoint is http://localhost:3000/mcp and the health endpoint is http://localhost:3000/health. Set PORT to change the port.

Docker
bash
docker build -t release-intel-mcp .docker run -p 3000:3000 \  -e GITHUB_TOKEN=your_read_only_token \  release-intel-mcp

Connect an HTTP client to http://localhost:3000/mcp.

Local development

bash
npm installnpm testnpm run buildGITHUB_TOKEN=your_read_only_token node dist/index.js

Requirements: Node.js 18 or newer.

See CONTRIBUTING.md for the development workflow.

Security and limits

  • Use a fine-grained, read-only token restricted to the required repositories.
  • The server never needs permission to write releases, issues, or pull requests.
  • GitHub's compare endpoint limits very large ranges. The response reports truncation.
  • Unlinked direct commits remain visible but cannot inherit pull request metadata.
  • Release categories are evidence-backed heuristics, not editorial conclusions.

License

MIT

Source: README.md at commit 721bc9a

Tools

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

Version history

1
  1. v0.7.2LatestSep 16, 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