release-intel
release-intel-mcp
一个从 GitHub 仓库数据生成发布情报的 MCP 服务器。它关联任意两个 git ref 之间的提交、拉取请求、问题与贡献者,并返回结构化上下文,供 AI 综合生成发布说明、变更日志和发布摘要。
工具
get_changes_between_refs
获取两个 git ref 之间的所有提交,并附带相关的 PR 元数据、作者信息和关联问题。
字段 | 类型 | 描述 |
| string | GitHub 仓库所有者或组织 |
| string | GitHub 仓库名称 |
| string | 基础 ref(较早的标签、分支或 SHA) |
| string | 目标 ref(较新的标签、分支或 SHA) |
get_pull_requests_in_range
获取两个 ref 之间所有已合并的 PR,并按标签自动分类为:breaking、feature、fix、docs、chore、dependencies、other。
输入字段与 get_changes_between_refs 相同。
get_release_summary
生成一个结构化的发布上下文对象,包含提交数据、PR 元数据、关联问题、贡献者列表和汇总统计。
字段 | 类型 | 描述 |
| string | GitHub 仓库所有者 |
| string | GitHub 仓库名称 |
| string | 上一个发布标签(基础) |
| string | 新的发布标签或 HEAD |
Related MCP server: MCP Releases Server
设置
所有选项都需要具有 repo 读取权限的 GitHub 个人访问令牌。
在此处生成:https://github.com/settings/tokens
选项 A:stdio(本地进程)
标准方式:MCP 客户端将服务器作为本地子进程启动。
Claude Desktop
配置文件:~/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
配置文件:~/.cursor/mcp.json
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Windsurf
配置文件:~/.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
配置文件:.vscode/mcp.json
{
"servers": {
"release-intel": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Cline
配置文件:~/.cline/mcp_settings.json(或通过 Cline 扩展设置界面)
{
"mcpServers": {
"release-intel": {
"command": "npx",
"args": ["-y", "@barissozudogru/release-intel-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Continue.dev
配置文件:~/.continue/config.yaml
mcpServers:
- name: release-intel
command: npx
args:
- -y
- "@barissozudogru/release-intel-mcp"
env:
GITHUB_TOKEN: ghp_your_tokenZed
配置文件:~/.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"
}
}
}
}选项 B:HTTP(远程 / 无状态)
将服务器作为 HTTP 端点运行。适用于远程客户端、团队共享部署,或偏好基于 URL 连接的客户端。
GITHUB_TOKEN=ghp_your_token npx @barissozudogru/release-intel-mcp --http默认在 3000 端口启动。设置 PORT 可更改端口。
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健康检查端点位于 GET /health。
选项 C:Docker
docker build -t release-intel-mcp .
docker run -p 3000:3000 -e GITHUB_TOKEN=ghp_your_token release-intel-mcp容器默认以 HTTP 模式启动。MCP 端点为 http://localhost:3000/mcp。
环境变量
变量 | 必需 | 默认值 | 描述 |
| 是 | - | GitHub 个人访问令牌(repo 范围) |
| 否 | stdio | 设置为 |
| 否 | 3000 | HTTP 端口(仅 HTTP 模式) |
本地开发
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许可证
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