Petri Labs

release engineering / Node.js and MCP

release-intel-mcp

Build release context from commits, pull requests, issues, and contributors.

release-intel-mcp gives MCP clients structured GitHub context between two refs. It correlates commits with merged pull requests, linked issues, labels, and authors so release notes can start from the repository record instead of a blank prompt.

npm packageSource on GitHubWorkflow note

Installation

npx -y @barissozudogru/release-intel-mcp

Platform requirements and configuration are documented in the repository instructions.

Capabilities

  • Compare any two tags, branches, or commit references
  • Enrich commits with pull request, issue, label, and contributor metadata
  • Group merged work into release-oriented categories
  • Return structured context for changelogs, summaries, and release review

Use cases

  • Preparing releases in repositories with active pull request workflows
  • Giving an MCP client auditable inputs for release-note drafting
  • Reviewing what changed across a tag or branch boundary

Evidence

verified public repository range

Fourteen commits become a bounded release evidence record.

The stable range v0.5.1 to commit 8a2f350 was inspected with the published server against its own public GitHub history.

commits    14
pull reqs  1
files      12
diff       +286 / -135
Inspect the source

GitHub Actions

Attach auditable release evidence to a workflow summary.

- uses: barissozudogru/[email protected]

Limitations

  • Requires GitHub read access for the repositories being inspected
  • Output quality depends on repository labels, issue links, and pull request hygiene
  • The server returns release context; a client still decides the final narrative
Full directory