Release Intel MCP Server

An MCP server that generates release intelligence from GitHub repository data. It correlates commits, pull requests, issues, and contributors between any two git refs and returns structured context ready for AI synthesis into release notes, changelogs, and release summaries. Its README documents 3 tools, including get_changes_between_refs, get_pull_requests_in_range, get_release_summary.

People connecting API integration tools to Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-20 · ★ 2 · #101 OF 250 MAINTAINED API INTEGRATION · VERIFIED 2026-08-25

MIT · JavaScript servers · how we verify → /methodology

01 · Install Release Intel

before you install - you'll need

GITHUB_TOKEN

Environment variables documented in the project's README - it lists which are required and which have defaults.

Claude Code

claude mcp add barissozudogru-release-intel-mcp -- npx -y @barissozudogru/release-intel-mcp

Claude Desktop / Cursor / VS Code - add to config

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

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @barissozudogru/release-intel-mcp - published under the repo owner's npm scope (@barissozudogru)

registry namespace io.github.barissozudogru is GitHub-verified and matches the repo owner

03 · What Release Intel can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can get all commits between two git refs enriched with associated PR metadata, author information, and linked issues, get all merged PRs between two refs, automatically categorized by label into: breaking, feature, fix, docs, chore, dependencies, other, and generate a structured release context object combining commit data, PR metadata, linked issues, contributor list, and aggregate statistics.

The 3 tools it gives your agent

Extracted from the project's README - what release-intel lets an agent do.

get_changes_between_refs
- Get all commits between two git refs enriched with associated PR metadata, author information, and linked issues.
get_pull_requests_in_range
- Get all merged PRs between two refs, automatically categorized by label into: breaking, feature, fix, docs, chore, dependencies, other.
get_release_summary
- Generate a structured release context object combining commit data, PR metadata, linked issues, contributor list, and aggregate statistics.

Latest releases

v0.5.1 · 2026-03-13

v0.5.0 · 2026-03-12

See CHANGELOG.md for details

v0.4.0 · 2026-03-12

See CHANGELOG.md for details

04 · Who maintains Release Intel

release-intel is maintained by barissozudogru. We track 3 MCP servers from barissozudogru - 3 actively maintained, 8 combined GitHub stars, oldest repo from Mar 2026. Full record: all servers from barissozudogru.

  1. test-intel Coverage analysis, untested function detection and complexity scoring for TS and JS. ★ 4
  2. gha-intel Workflow timing analysis, configuration audit and billing insight for GitHub Actions. ★ 2

05 · Facts

category
API integration - ranked #101 of 250 actively-maintained API integration servers as of 2026-08-25.
registry
io.github.barissozudogru/release-intel (active, first published 2026-08-20)
packages
npm:@barissozudogru/release-intel-mcp

06 · Release Intel FAQ

Is Release Intel still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-20. We re-verify nightly.

What can Release Intel do?

With this server connected, an agent can get all commits between two git refs enriched with associated PR metadata, author information, and linked issues, get all merged PRs between two refs, automatically categorized by label into: breaking, feature, fix, docs, chore, dependencies, other, and generate a structured release context object combining commit data, PR metadata, linked issues, contributor list, and aggregate statistics.

How do I install Release Intel?

Run `npx -y @barissozudogru/release-intel-mcp`. The README documents one environment variable (GITHUB_TOKEN) to set first. You can also paste the ready-made client config above.

Does Release Intel run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Release Intel