Back to Browse
Local development —
Run with
Free
Server data from the Official MCP Registry
A small, generic MCP server for combining GitHub/GitLab/Gitea releases into product release notes
About
A small, generic MCP server for combining GitHub/GitLab/Gitea releases into product release notes
Security Report
8.2
Low Risk8.2Low RiskA well-designed MCP server for aggregating release notes with proper security practices. Authentication is correctly delegated to environment variables, permissions are appropriately scoped to configured repositories, and input validation prevents unauthorized access. Minor code quality suggestions exist (exception handling specificity, logging) but do not present security risks. Package verification found 1 issue.
4 files analyzed · 4 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
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.
Environment variable: RELEASE_MCP_CONFIG_JSON
Absolute path to a config.json file (alternative to RELEASE_MCP_CONFIG_JSON). Used when mounting a real file, e.g. in Docker.
Environment variable: RELEASE_MCP_CONFIG
Auth token for the provider (GitHub PAT / GitLab / Gitea token). Optional for public repos.Required
Environment variable: TOKEN
Forge to read releases from: github | gitlab | gitea. Defaults to github.
Environment variable: PROVIDER
API base URL — only for self-hosted GitLab or Gitea/Forgejo.
Environment variable: BASE_URL
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-vaggeliskls-release-notes-mcp": {
"env": {
"TOKEN": "your-token-here",
"BASE_URL": "your-base-url-here",
"PROVIDER": "your-provider-here",
"RELEASE_MCP_CONFIG": "your-release-mcp-config-here",
"RELEASE_MCP_CONFIG_JSON": "your-release-mcp-config-json-here"
},
"args": [
"release-notes-mcp"
],
"command": "uvx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
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, orgitea/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 |
formaton a context source is optional — auto-detected fromContent-Type/ URL extension / content sniffing. Override only when wrong.
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."
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
80.0K
Stars
5
Installs
5.3
Security
No ratings yet
Local
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
80.0K
Stars
6
Installs
6.5
Security
No ratings yet
Local
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
137
Stars
532
Installs
8.0
Security
4.8
Local