release-notes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKEN | No | Auth token for the provider (optional for public repos) | |
| BASE_URL | No | API base URL for self-hosted GitLab/Gitea (default: provider default) | |
| PROVIDER | No | Provider: github, gitlab, or gitea (default: github) | |
| RELEASE_MCP_CONFIG | No | Path to config.json file | |
| RELEASE_MCP_CONFIG_JSON | No | Inline JSON config with repos and contextSources |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reposA | List the repositories and provider this server is configured to read. |
| list_releasesA | List recent releases for one repo (newest first). By default the release |
| get_latest_versionA | Get the latest published release for one repo. |
| get_releaseB | Get the full release notes for a specific tag in one repo. |
| compare_releasesA | Return every release in Bodies are omitted by default (pass |
| gather_release_notesA | Bundle raw release notes for an explicit list of selections so they can be synthesized into a single product release.
|
| get_contextA | Load supplementary context the user configured in Call this first when assembling release notes. With no argument it loads all
sources; pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: repo discovery, release listing, latest version, specific release, range comparison, bulk gathering, and context loading. No two tools appear to serve the same purpose.
All tool names follow a consistent snake_case verb_noun pattern: list_repos, list_releases, get_latest_version, get_release, compare_releases, gather_release_notes, get_context. Naming style is uniform and predictable.
Seven tools is well within the ideal 3-15 range for a focused release-notes server. Each tool earns its place with a clear role in the workflow.
The tool surface covers the full release-notes lifecycle: discovering repositories, listing and filtering releases, drilling into specific versions, comparing ranges, bundling multiple notes, and pulling supplementary context. No obvious operational gap remains.