Release Notes MCP

Name: Release Notes MCP
Author: vaggeliskls

作者：vaggeliskls版本 1.0.1i★ –i在你的电脑上运行

注册名称io.github.vaggeliskls/release-notes-mcp

安装

概览

作者提供的说明（英文原文）

A small, generic MCP server for combining GitHub/GitLab/Gitea releases into product release notes

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 20/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 文档、表格与办公
你需要填写：TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： RELEASE_MCP_CONFIG_JSON, RELEASE_MCP_CONFIG, TOKEN, PROVIDER, BASE_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "release-notes": {
      "command": "uvx",
      "args": [
        "release-notes-mcp"
      ],
      "env": {
        "RELEASE_MCP_CONFIG_JSON": "your-value",
        "RELEASE_MCP_CONFIG": "your-value",
        "TOKEN": "your-value",
        "PROVIDER": "your-value",
        "BASE_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add release-notes --env RELEASE_MCP_CONFIG_JSON=your-value --env RELEASE_MCP_CONFIG=your-value --env TOKEN=your-value --env PROVIDER=your-value --env BASE_URL=your-value -- uvx release-notes-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "release-notes": {
      "command": "uvx",
      "args": [
        "release-notes-mcp"
      ],
      "env": {
        "RELEASE_MCP_CONFIG_JSON": "your-value",
        "RELEASE_MCP_CONFIG": "your-value",
        "TOKEN": "your-value",
        "PROVIDER": "your-value",
        "BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "release-notes": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "release-notes-mcp"
      ],
      "env": {
        "RELEASE_MCP_CONFIG_JSON": "your-value",
        "RELEASE_MCP_CONFIG": "your-value",
        "TOKEN": "your-value",
        "PROVIDER": "your-value",
        "BASE_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

RELEASE_MCP_CONFIG_JSON env
Config (repos + contextSources) as inline JSON, e.g. {"repos":["myorg/web"],"contextSources":[]}. Use this for uvx/hub launches with no file to mount. Either this or RELEASE_MCP_CONFIG is required.
RELEASE_MCP_CONFIG env
Absolute path to a config.json file (alternative to RELEASE_MCP_CONFIG_JSON). Used when mounting a real file, e.g. in Docker.
TOKEN 机密 env
Auth token for the provider (GitHub PAT / GitLab / Gitea token). Optional for public repos.
PROVIDER env
Forge to read releases from: github | gitlab | gitea. Defaults to github.
BASE_URL env
API base URL — only for self-hosted GitLab or Gitea/Forgejo.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 vaggeliskls 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

星标数多于此分类中其他 3677 个服务器的 0%
发布到注册中心的时间比此分类中其他 3677 个服务器的 15% 更新
基础检查结果等于或优于此分类中其他 3677 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Release Notes MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.1）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

Agent-Native Google Calendar - manage events, sync, and public booking

作者：BuilderIO正在增长★ 76202个月前更新

在云端运行

安装

Excel MCP Server

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

作者：haris-musa广泛使用↓ 5万/周★ 4276昨天更新

在你的电脑上运行

安装

MCP Server for Excel

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

作者：sbroenne正在增长↓ 4321/周★ 847今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

release-notes-mcp

A small, generic MCP server that combines GitHub releases from several repositories into a single product release note. The server just fetches and bundles raw data; the LLM synthesizes the final notes.

Nothing is architecture-specific:

`provider` — which forge to read releases from: github (default), gitlab, or gitea/Forgejo. Release fetching goes through a small adapter, so adding a forge means normalizing its release JSON — a contained change.
`repos` — the repos the server is allowed to read releases from.
`contextSources` — arbitrary URLs loaded as background context (a style guide, a versions file, feature names — anything). The server assigns no meaning; what each source *is* is decided by what you put behind the URL.

Configuration

Config holds no secrets — only the repo set and context. Provider and auth come from the environment.

// config.json — non-sensitive (required; the server errors if it's missing)

{ "repos": [ "myorg/auth-service", "myorg/web" ], "contextSources": [ { "name": "release-info", "url": "https://example.github.io/whatever/release.json", "description": "Extra context to consult when assembling release notes" } ] }

Environment (provider-agnostic, set in .env or your shell):

Var	Purpose	Default
`TOKEN`	Auth token for the provider — never in config	_(empty; ok for public repos)_
`PROVIDER`	`github` \	`gitlab` \	`gitea` (overrides config)	`github`
`BASE_URL`	API base — only for self-hosted GitLab / Gitea	provider default

format on a context source is optional — auto-detected from Content-Type / URL extension / content sniffing. Override only when wrong.

Token permissions

The server only ever reads releases (GET /repos/{owner}/{repo}/releases…), so give TOKEN the minimum read scope — never write access.

Provider	Public repos	Private repos
GitHub — fine-grained PAT	no token needed	Contents: Read-only (releases live under Contents), for each repo you list
GitHub — classic PAT	no token needed (or `public_repo`)	`repo` scope
GitLab	no token needed	`read_api` scope
Gitea / Forgejo	no token needed	`read:repository` scope

For GitHub, a fine-grained PAT scoped to just the repos in config.json with Contents → Read-only is the tightest setup and is all this server requires.

The config (repos + contextSources) must come from one of two places — the server errors on startup if neither is set:

Source	Use it for
`RELEASE_MCP_CONFIG_JSON`	The config as inline JSON. No file needed — ideal for `uvx` / MCP hubs where everything is an env var.
`RELEASE_MCP_CONFIG`	Path to a `config.json` file (default `./config.json`). Used by the container, which mounts a real file.

Inline JSON wins when both are set. Copy config.example.json to get started with the file approach.

Tools

Tool	Purpose
`list_repos()`	The configured repos
`list_releases(repo, limit)`	Recent releases for one repo
`get_latest_version(repo)`	Newest release for one repo
`get_release(repo, tag)`	Full notes for one tag
`compare_releases(repo, from_tag, to_tag)`	All releases between two versions
`gather_release_notes(selections[])`	Bundle raw notes from N `(repo, tag)` pairs (concurrent)
`get_context(name?)`	Load configured context URLs (auto-detected format)

Selection is dynamic — you (or Claude) pass the (repo, tag) pairs to combine. The server's instructions tell Claude to call get_context() first.

Run

The server runs in a container over HTTP transport on localhost:8000. First create the config and env files (both runs need them):

cp config.example.json config.json   # edit repos + contextSources (no secrets)

cp .env.example .env # set TOKEN (+ PROVIDER / BASE_URL if needed)

Normal run

docker compose up -d

Local development — `docker compose watch`

For local dev, docker compose watch keeps the server live while you edit:

docker compose watch

Change	Action
`server.py`	sync + restart — copied into the container, process restarts
`requirements.txt`, `Dockerfile`	rebuild — image is rebuilt automatically
`config.json`	bind-mounted (live); run `docker compose restart` to reload it

Run with `uvx` (no clone, no container)

The server is published to PyPI, so a client can launch it on demand with uvx — no checkout and no Docker:

uvx release-notes-mcp

uvx talks to the server over stdio (the default transport). Since there's no file to mount, pass the config inline as JSON via RELEASE_MCP_CONFIG_JSON (everything is env-only — ideal for MCP hubs):

RELEASE_MCP_CONFIG_JSON='{"repos":["myorg/web"],"contextSources":[]}' \

TOKEN=ghp_... uvx release-notes-mcp

Prefer a file? Point RELEASE_MCP_CONFIG at an absolute path instead (uvx runs from an unknown working directory, so a relative path won't resolve):

RELEASE_MCP_CONFIG=/abs/path/config.json TOKEN=ghp_... uvx release-notes-mcp

Register with Claude Code

HTTP (container) — point Claude Code at the running server by its URL:

claude mcp add --transport http release-notes http://localhost:8000/mcp

stdio (`uvx`) — let Claude Code launch the server as a subprocess:

claude mcp add release-notes \

--env RELEASE_MCP_CONFIG=/abs/path/config.json \ --env TOKEN=ghp_... \ -- uvx release-notes-mcp

Then ask Claude: *"Combine the latest releases of auth-service and web into a product release note."*