release-intel
Generates release intelligence from GitHub repository data by correlating commits, pull requests, issues, and contributors between refs, providing structured context for release notes, changelogs, and release summaries.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@release-intelWhat changed between v1.0.0 and v2.0.0 for the repo acme/webapp?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
release-intel-mcp
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.
Tools
get_changes_between_refs
Get all commits between two git refs enriched with associated PR metadata, author information, and linked issues.
Field | Type | Description |
| string | GitHub repository owner or organization |
| string | GitHub repository name |
| string | Base ref (older tag, branch, or SHA) |
| string | Head ref (newer tag, branch, or SHA) |
get_pull_requests_in_range
Get all merged PRs between two refs, automatically categorized by label into: breaking, feature, fix, docs, chore, dependencies, other.
Input fields are identical to get_changes_between_refs.
get_release_summary
Generate a structured release context object combining commit data, PR metadata, linked issues, contributor list, and aggregate statistics.
Field | Type | Description |
| string | GitHub repository owner |
| string | GitHub repository name |
| string | Previous release tag (base) |
| string | New release tag or HEAD |
Related MCP server: MCP Releases Server
Setup
All options require a GitHub personal access token with repo read access.
Generate one at: https://github.com/settings/tokens
Option A: stdio (local process)
The standard approach: the MCP client spawns the server as a local subprocess.
Claude Desktop
Config file: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Claude Code
claude mcp add release-intel -e GITHUB_TOKEN=ghp_your_token -- npx -y @barissozudogru/release-intel-mcpCursor
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Windsurf
Config file: ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}VS Code + Copilot
Config file: .vscode/mcp.json
{
"servers": {
"release-intel": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Cline
Config file: ~/.cline/mcp_settings.json (or via the Cline extension settings UI)
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Continue.dev
Config file: ~/.continue/config.yaml
mcpServers:
- name: release-intel
command: npx
args:
- -y
- "@barissozudogru/release-intel-mcp"
env:
GITHUB_TOKEN: ghp_your_tokenZed
Config file: ~/.config/zed/settings.json
{
"context_servers": {
"release-intel": {
"command": {
"path": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}
}JetBrains (AI Assistant plugin)
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Option B: HTTP (remote / stateless)
Run the server as an HTTP endpoint. Useful for remote clients, shared team deployments, or clients that prefer URL-based connections.
GITHUB_TOKEN=ghp_your_token npx @barissozudogru/release-intel-mcp --httpBy default this starts on port 3000. Set PORT to change it.
Cursor (HTTP)
{
"mcpServers": {
"release-intel": {
"url": "http://localhost:3000/mcp"
}
}
}VS Code + Copilot (HTTP)
{
"servers": {
"release-intel": {
"type": "http",
"url": "http://localhost:3000/mcp"
}
}
}Windsurf (HTTP)
{
"mcpServers": {
"release-intel": {
"serverUrl": "http://localhost:3000/mcp"
}
}
}Continue.dev (HTTP)
mcpServers:
- name: release-intel
type: streamable-http
url: http://localhost:3000/mcpA health check endpoint is available at GET /health.
Option C: Docker
docker build -t release-intel-mcp .
docker run -p 3000:3000 -e GITHUB_TOKEN=ghp_your_token release-intel-mcpThe container starts in HTTP mode by default. The MCP endpoint is at http://localhost:3000/mcp.
Environment Variables
Variable | Required | Default | Description |
| Yes | - | GitHub personal access token (repo scope) |
| No | stdio | Set to |
| No | 3000 | HTTP port (HTTP mode only) |
Local Development
git clone https://github.com/barissozudogru/release-intel-mcp.git
cd release-intel-mcp
npm install
npm run build
GITHUB_TOKEN=ghp_... node dist/index.jsLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseCqualityAmaintenanceA MCP server that bridges LLMs with GitHub repository management, enabling automated analysis of pull requests, issue management, tag creation, and release management through natural language.246Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides GitHub release information through the Model Context Protocol. It features a tool to retrieve the latest stable release version of any specified GitHub repository.
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that provides AI assistants with comprehensive GitHub developer tooling including PR analysis, code review, changelog generation, dependency auditing, commit summarization, and refactoring suggestions.13ISC
- AlicenseAqualityCmaintenanceMCP server for developer workflow automation — smart commits, secret scanning, PR descriptions, and more.5MIT
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
An MCP server that gives your AI access to the source code and docs of all public github repos
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/barissozudogru/release-intel-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server