Release Intel MCP Server

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. Its README documents 3 tools, including get_changes_between_refs, get_pull_requests_in_range, get_release_summary.

People who work with changelog, developer tools and github and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-26 · ★ 2 · #86 OF 278 MAINTAINED API INTEGRATION · VERIFIED 2026-09-18

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

An agent gets 3 documented tools, including get_changes_between_refs, get_pull_requests_in_range, get_release_summary.

The 3 tools it gives your agent

Extracted from the project's README - what Release Intel lets an agent do.

get_changes_between_refs: - Commits enriched with merged pull request metadata and linked issues
get_pull_requests_in_range: - Merged pull requests grouped as breaking, feature, fix, docs, chore, dependency, release, or other
get_release_summary: - A complete release evidence object with aggregate statistics and contributors

Latest releases

v0.7.2 · 2026-08-26

v0.7.1 · 2026-08-26

v0.7.0 · 2026-08-25

Publish to the registry the workflow authenticates against

04 · Who maintains Release Intel

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

05 · Facts

repository: github.com/barissozudogru/release-intel-mcp
website: https://petri-labs.org/tools/release-intel-mcp/
category: API integration - ranked #86 of 278 actively-maintained API integration servers as of 2026-09-18.
release cadence: 3 releases in the last 90 days (latest 2026-08-26)
registry: io.github.barissozudogru/release-intel (active, first published 2026-08-20 · 4 versions)
packages: npm:@barissozudogru/release-intel-mcp

06 · Release Intel FAQ

Is Release Intel still maintained?

Yes - as of 2026-09-18, its last commit was 2026-08-26 and it shipped 3 releases in the last 90 days. We re-verify nightly.

What can Release Intel do?

An agent gets 3 documented tools, including get_changes_between_refs, get_pull_requests_in_range, get_release_summary.

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

Alternatives to Release Intel

Maintained API integration servers if Release Intel isn't the fit.

More API integration MCP servers · VRChat MCP · OpenSTAAD MCP Server · Genefoundry · Easy Bits · Boostu Teamleader MCP

More JavaScript MCP servers · Stablecoin Yield · Ffmpeg Render Pro · Bugherd MCP · Displaybuddy MCP · Token Tool · see all