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.
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.
observed output
commits 14pull reqs 1files 12diff +286 / -135
what it exposes
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
workflow integration
Keep the evidence in the run
Attach auditable release evidence to a workflow summary.
- uses: barissozudogru/release-intel-mcp@v0.7.2good fit
Use it when
- 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
operating limits
Know before using
- 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