Release Notes MCP

Name: Release Notes MCP
Author: vaggeliskls

by vaggelisklsversion 1.0.1i★ –iRuns on your computer

Registry nameio.github.vaggeliskls/release-notes-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work
You need to fill in: TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: RELEASE_MCP_CONFIG_JSON, RELEASE_MCP_CONFIG, TOKEN, PROVIDER, BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
      }
    }
  }
}

Run this in your terminal

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account vaggeliskls, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 2188 servers in this category
Published to the registry more recently than 16% of the other 2188 servers in this category
Basic checks equal to or better than 100% of the other 2188 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Release Notes MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

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

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 6 days ago

Install

MCP Server for Excel

by sbroenne

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

Runs on your computer★ 847MITUpdated 3 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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."*

Release Notes MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

release-notes-mcp

Configuration

Token permissions

Tools

Run

Normal run

Local development — docker compose watch

Run with uvx (no clone, no container)

Register with Claude Code

Local development — `docker compose watch`

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