Skip to main content
Glama

release-intel-mcp

Un servidor MCP que genera inteligencia de lanzamiento a partir de datos de repositorios de GitHub. Correlaciona commits, pull requests, issues y contribuidores entre dos refs de git y devuelve contexto estructurado listo para la síntesis por IA en notas de lanzamiento, changelogs y resúmenes de lanzamiento.


Herramientas

get_changes_between_refs

Obtén todos los commits entre dos refs de git enriquecidos con metadatos de PR asociados, información del autor e issues vinculados.

Campo

Tipo

Descripción

owner

string

Propietario u organización del repositorio de GitHub

repo

string

Nombre del repositorio de GitHub

base

string

Ref base (tag, rama o SHA más antiguo)

head

string

Ref head (tag, rama o SHA más reciente)

get_pull_requests_in_range

Obtén todos los PR fusionados entre dos refs, categorizados automáticamente por etiqueta en: breaking, feature, fix, docs, chore, dependencies, other.

Los campos de entrada son idénticos a get_changes_between_refs.

get_release_summary

Genera un objeto de contexto de lanzamiento estructurado que combina datos de commits, metadatos de PR, issues vinculados, lista de contribuidores y estadísticas agregadas.

Campo

Tipo

Descripción

owner

string

Propietario del repositorio de GitHub

repo

string

Nombre del repositorio de GitHub

from_tag

string

Tag de lanzamiento anterior (base)

to_tag

string

Nuevo tag de lanzamiento o HEAD


Related MCP server: MCP Releases Server

Configuración

Todas las opciones requieren un token de acceso personal de GitHub con acceso de lectura a repo. Genera uno en: https://github.com/settings/tokens


Opción A: stdio (proceso local)

El enfoque estándar: el cliente MCP inicia el servidor como un subproceso local.

Claude Desktop

Archivo de configuración: ~/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-mcp

Cursor

Archivo de configuración: ~/.cursor/mcp.json

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

Windsurf

Archivo de configuración: ~/.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

Archivo de configuración: .vscode/mcp.json

{
  "servers": {
    "release-intel": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@barissozudogru/release-intel-mcp"],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token"
      }
    }
  }
}

Cline

Archivo de configuración: ~/.cline/mcp_settings.json (o mediante la interfaz de configuración de la extensión Cline)

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

Continue.dev

Archivo de configuración: ~/.continue/config.yaml

mcpServers:
  - name: release-intel
    command: npx
    args:
      - -y
      - "@barissozudogru/release-intel-mcp"
    env:
      GITHUB_TOKEN: ghp_your_token

Zed

Archivo de configuración: ~/.config/zed/settings.json

{
  "context_servers": {
    "release-intel": {
      "command": {
        "path": "npx",
        "args": ["-y", "@barissozudogru/release-intel-mcp"],
        "env": {
          "GITHUB_TOKEN": "ghp_your_token"
        }
      }
    }
  }
}

JetBrains (plugin AI Assistant)

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

Opción B: HTTP (remoto / sin estado)

Ejecuta el servidor como un endpoint HTTP. Útil para clientes remotos, despliegues de equipos compartidos o clientes que prefieren conexiones basadas en URL.

GITHUB_TOKEN=ghp_your_token npx @barissozudogru/release-intel-mcp --http

Por defecto, esto se inicia en el puerto 3000. Configura PORT para cambiarlo.

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/mcp

Un endpoint de verificación de salud está disponible en GET /health.


Opción C: Docker

docker build -t release-intel-mcp .
docker run -p 3000:3000 -e GITHUB_TOKEN=ghp_your_token release-intel-mcp

El contenedor se inicia en modo HTTP por defecto. El endpoint MCP está en http://localhost:3000/mcp.


Variables de Entorno

Variable

Requerida

Por defecto

Descripción

GITHUB_TOKEN

Sí

-

Token de acceso personal de GitHub (alcance de repo)

TRANSPORT

No

stdio

Configúralo en http para habilitar el modo HTTP

PORT

No

3000

Puerto HTTP (solo modo HTTP)


Desarrollo Local

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.js

Licencia

MIT

Available Tools

3 tools
get_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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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