Skip to main content
ClaudeWave

MCP server for release intelligence: correlates commits, PRs, issues, and contributors between two git refs

MCP ServersRegistry oficial2 estrellas0 forksJavaScriptMITActualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 8/21/2026
Install in Claude Code / Claude Desktop
Method: NPX · @barissozudogru/release-intel-mcp
Claude Code CLI
claude mcp add release-intel-mcp -- npx -y @barissozudogru/release-intel-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "release-intel-mcp": {
      "command": "npx",
      "args": ["-y", "@barissozudogru/release-intel-mcp"],
      "env": {
        "GITHUB_TOKEN": "<github_token>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Detected environment variables
GITHUB_TOKEN
Casos de uso

Resumen de MCP Servers

# 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                              |
|---------|--------|------------------------------------------|
| `owner` | string | GitHub repository owner or organization |
| `repo`  | string | GitHub repository name                   |
| `base`  | string | Base ref (older tag, branch, or SHA)     |
| `head`  | 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                     |
|------------|--------|---------------------------------|
| `owner`    | string | GitHub repository owner         |
| `repo`     | string | GitHub repository name          |
| `from_tag` | string | Previous release tag (base)     |
| `to_tag`   | string | New release tag or HEAD         |

---

## 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`

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

#### Claude Code

```bash
claude mcp add release-intel -e GITHUB_TOKEN=ghp_your_token -- npx -y @barissozudogru/release-intel-mcp
```

#### Cursor

Config file: `~/.cursor/mcp.json`

```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`

```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`

```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)

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

#### Continue.dev

Config file: `~/.continue/config.yaml`

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

#### Zed

Config file: `~/.config/zed/settings.json`

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

#### JetBrains (AI Assistant plugin)

```json
{
  "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.

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

By default this starts on port 3000. Set `PORT` to change it.

#### Cursor (HTTP)

```json
{
  "mcpServers": {
    "release-intel": {
      "url": "http://localhost:3000/mcp"
    }
  }
}
```

#### VS Code + Copilot (HTTP)

```json
{
  "servers": {
    "release-intel": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    }
  }
}
```

#### Windsurf (HTTP)

```json
{
  "mcpServers": {
    "release-intel": {
      "serverUrl": "http://localhost:3000/mcp"
    }
  }
}
```

#### Continue.dev (HTTP)

```yaml
mcpServers:
  - name: release-intel
    type: streamable-http
    url: http://localhost:3000/mcp
```

A health check endpoint is available at `GET /health`.

---

### Option C: Docker

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

The container starts in HTTP mode by default. The MCP endpoint is at `http://localhost:3000/mcp`.

---

## Environment Variables

| Variable       | Required | Default | Description                               |
|----------------|----------|---------|-------------------------------------------|
| `GITHUB_TOKEN` | Yes      | -       | GitHub personal access token (repo scope) |
| `TRANSPORT`    | No       | stdio   | Set to `http` to enable HTTP mode         |
| `PORT`         | No       | 3000    | HTTP port (HTTP mode only)                |

---

## Local Development

```bash
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
```

---

## License

MIT
changelogdeveloper-toolsgithubgithub-apimcpmcp-servermodel-context-protocolrelease-managementrelease-notestypescript

Lo que la gente pregunta sobre release-intel-mcp

¿Qué es barissozudogru/release-intel-mcp?

+

barissozudogru/release-intel-mcp es mcp servers para el ecosistema de Claude AI. MCP server for release intelligence: correlates commits, PRs, issues, and contributors between two git refs Tiene 2 estrellas en GitHub y su última actualización registrada es del 2026-08-20.

¿Cómo se instala release-intel-mcp?

+

Puedes instalar release-intel-mcp clonando el repositorio (https://github.com/barissozudogru/release-intel-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar barissozudogru/release-intel-mcp?

+

Nuestro agente de seguridad ha analizado barissozudogru/release-intel-mcp y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene barissozudogru/release-intel-mcp?

+

barissozudogru/release-intel-mcp es mantenido por barissozudogru. La última actividad registrada en GitHub es del 2026-08-20, con 0 issues abiertos.

¿Hay alternativas a release-intel-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega release-intel-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: barissozudogru/release-intel-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/barissozudogru-release-intel-mcp)](https://claudewave.com/repo/barissozudogru-release-intel-mcp)
<a href="https://claudewave.com/repo/barissozudogru-release-intel-mcp"><img src="https://claudewave.com/api/badge/barissozudogru-release-intel-mcp" alt="Featured on ClaudeWave: barissozudogru/release-intel-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a release-intel-mcp