release-intel
release-intel-mcp
Ein MCP-Server, der Release-Intelligence aus GitHub-Repository-Daten generiert. Er korreliert Commits, Pull Requests, Issues und Mitwirkende zwischen zwei beliebigen Git-Refs und liefert strukturierten Kontext, der für die KI-Synthese zu Release-Notes, Changelogs und Release-Zusammenfassungen bereit ist.
Werkzeuge
get_changes_between_refs
Ruft alle Commits zwischen zwei Git-Refs ab, angereichert mit zugehörigen PR-Metadaten, Autoreninformationen und verknüpften Issues.
Feld | Typ | Beschreibung |
| string | GitHub-Repository-Besitzer oder -Organisation |
| string | GitHub-Repository-Name |
| string | Basis-Ref (älterer Tag, Branch oder SHA) |
| string | Head-Ref (neuerer Tag, Branch oder SHA) |
get_pull_requests_in_range
Ruft alle gemergten PRs zwischen zwei Refs ab, automatisch nach Label kategorisiert in: breaking, feature, fix, docs, chore, dependencies, other.
Die Eingabefelder sind identisch mit get_changes_between_refs.
get_release_summary
Erzeugt ein strukturiertes Release-Kontextobjekt, das Commit-Daten, PR-Metadaten, verknüpfte Issues, Mitwirkendenliste und aggregierte Statistiken kombiniert.
Feld | Typ | Beschreibung |
| string | GitHub-Repository-Besitzer |
| string | GitHub-Repository-Name |
| string | Vorheriges Release-Tag (Basis) |
| string | Neues Release-Tag oder HEAD |
Related MCP server: MCP Releases Server
Einrichtung
Alle Optionen erfordern ein persönliches GitHub-Zugriffstoken mit Lesezugriff auf repo. Erstellen Sie eines unter: https://github.com/settings/tokens
Option A: stdio (lokaler Prozess)
Der Standardansatz: Der MCP-Client startet den Server als lokalen Unterprozess.
Claude Desktop
Konfigurationsdatei: ~/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
Konfigurationsdatei: ~/.cursor/mcp.json
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Windsurf
Konfigurationsdatei: ~/.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
Konfigurationsdatei: .vscode/mcp.json
{
"servers": {
"release-intel": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Cline
Konfigurationsdatei: ~/.cline/mcp_settings.json (oder über die Einstellungs-UI der Cline-Erweiterung)
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Continue.dev
Konfigurationsdatei: ~/.continue/config.yaml
mcpServers:
- name: release-intel
command: npx
args:
- -y
- "@barissozudogru/release-intel-mcp"
env:
GITHUB_TOKEN: ghp_your_tokenZed
Konfigurationsdatei: ~/.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 / zustandslos)
Führen Sie den Server als HTTP-Endpunkt aus. Nützlich für Remote-Clients, gemeinsame Team-Bereitstellungen oder Clients, die URL-basierte Verbindungen bevorzugen.
GITHUB_TOKEN=ghp_your_token npx @barissozudogru/release-intel-mcp --httpStandardmäßig startet dies auf Port 3000. Setzen Sie PORT, um ihn zu ändern.
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/mcpEin Health-Check-Endpunkt ist unter GET /health verfügbar.
Option C: Docker
docker build -t release-intel-mcp .
docker run -p 3000:3000 -e GITHUB_TOKEN=ghp_your_token release-intel-mcpDer Container startet standardmäßig im HTTP-Modus. Der MCP-Endpunkt befindet sich unter http://localhost:3000/mcp.
Umgebungsvariablen
Variable | Erforderlich | Standard | Beschreibung |
| Ja | - | Persönlicher GitHub-Zugriffstoken (Repo-Bereich) |
| Nein | stdio | Auf |
| Nein | 3000 | HTTP-Port (nur HTTP-Modus) |
Lokale Entwicklung
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.jsLizenz
MIT
Available Tools
3 toolsget_changes_between_refsGet Changes Between RefsB
Get all commits between two git refs enriched with associated PR metadata, author information, and linked issues. Uses the GitHub compare API.
Inputs: base (required), head (required), repo (required), owner (required).
get_pull_requests_in_rangeGet Pull Requests in RangeA
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.
Inputs: base (required), head (required), repo (required), owner (required).
get_release_summaryGet Release SummaryA
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.
Inputs: repo (required), owner (required), to_tag (required), from_tag (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The three tools are largely distinct: one fetches commits, one fetches PRs, and one combines both into a summary. However, get_changes_between_refs and get_pull_requests_in_range both retrieve PR-related data, which could cause slight confusion for an agent deciding between them. The descriptions provide enough clarity to mitigate overlap.
All tool names follow a consistent 'get_' verb prefix followed by descriptive noun phrases in snake_case (changes_between_refs, pull_requests_in_range, release_summary). This pattern is predictable and aligns with common conventions.
With only 3 tools, the server is lean but each tool serves a clear purpose in the release-intel workflow: retrieving commits, retrieving PRs, and generating a summary. The count is minimal yet sufficient for the stated domain, though it sits at the low end of the ideal range.
The server covers the core operations for generating release context: commits, PRs, and a combined summary. However, there is no tool to list available tags/refs, which would be a natural precursor to using the other tools, and no way to directly fetch issues outside of PRs. These gaps could require agents to work around them.
Maintenance
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
Create, deploy, and operate MCP servers directly from your GitHub repositories.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Repository knowledge graph MCP server for codebase understanding and debugging.
Related MCP Servers
- AlicenseAqualityBmaintenanceA 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.446Apache 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.MIT
- AlicenseAqualityDmaintenanceMCP server for developer workflow automation — smart commits, secret scanning, PR descriptions, and more.5MIT