Mmcp.market

Release Intel MCP server

by barissozudogru·io.github.barissozudogru/release-intel·v0.7.2

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

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

2 stars32 downloads/wk

Reviews

Write one

Nobody has reviewed Release Intel yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Release Intel tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_changes_between_refs

    Get all commits between two git refs enriched with associated PR metadata, author information, and linked issues. Uses the GitHub compare API.

  • get_pull_requests_in_range

    Get all merged pull requests between two refs with full metadata including labels, linked issues, review counts, and files changed. PRs are categorized by label into: breaking, feature, fix, docs, chore, dependencies, other.

  • get_release_summary

    Generate a structured release context object ready for AI synthesis into release notes. Combines commit data, PR metadata, linked issues, contributor list, and aggregate statistics for the range between two tags.

Public scan report

scanner v0.1.9 · 2026-09-21 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • Live reliabilityno gateway calls yet and no remote to proben/a
  • Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 26 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Release Intel repository's README, as published. We do not edit it. Read it on GitHub

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.

{
  "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:

Use release-intel to build release evidence for owner/repository
from v1.4.0 to v1.5.0. Separate merged PRs from direct commits
and 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:

Repository:        barissozudogru/release-intel-mcp
Commits:           14
Merged PRs:        1
Files changed:     12
Lines added:       286
Lines deleted:     135
Contributors:      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

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:

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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y @barissozudogru/release-intel-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add release-intel -- npx -y @barissozudogru/release-intel-mcp
Add to Cursor

Release Intel: common questions

Is Release Intel MCP server safe?
Mostly: it is graded B (83/100). Read the Release Intel safety report
How do I install Release Intel?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Release Intel need an API key?
Yes. The registry entry asks for GITHUB_TOKEN.
Is Release Intel maintained?
The last commit was 26 days ago (2026-08-26). The latest release is v0.7.2.
What can I use instead of Release Intel?
Servers from other publishers that do the same job: Gitlab MCP server, GitHub MCP server and Quilt MCP server. Compare all Release Intel alternatives.

Alternatives to Release Intel

Same job from other publishers: the closest match first, then the best rated.

All Release Intel alternatives →
  • Gitlab
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Quilt
    Track which AI agent wrote which lines in a shared Git checkout; each commits only its own lines.
    A
  • Baron
    Let your coding agent write to your work tracker: issues, branches, PRs and CI, one contract.
    A
  • Repo Release Tools
    Config-driven branch and release helpers for Git repositories
    A

More from barissozudogru