breaking-changes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GH_TOKEN | No | Alternative environment variable for GitHub token. | |
| GITHUB_TOKEN | No | Personal access token to raise GitHub API limits (60→5000/hr). Read-only, no scopes needed for public repos. | |
| NPM_REGISTRY | No | Override for private/mirror registries. | https://registry.npmjs.org |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| breaking_changes_betweenA | Get an accurate, source-grounded list of BREAKING CHANGES for an npm package between two versions. Reach for this BEFORE writing or reviewing any dependency upgrade / migration — it defeats the model's stale, hallucinated migration knowledge by reading the real GitHub release notes (and CHANGELOG as fallback) for every version in the range. Returns breaking notes grouped per version, newest first. |
| changelog_betweenA | Return the complete release notes (not just breaking lines) for every version of an npm package between |
| list_versionsA | List published versions of an npm package with their release dates, newest first. Use this to discover valid |
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 3 tools
Each tool has a clearly distinct purpose: listing versions, fetching breaking changes, and fetching full changelog. The overlap between breaking_changes_between and changelog_between is well-defined, with descriptions explicitly stating breaking-only vs full release notes, so agents should not confuse them.
All names use snake_case and are descriptive, but there is a minor mix: list_versions follows verb_noun while the other two follow noun_preposition. The '_between' suffix is consistent for the pair, making the set predictable overall.
Three tools is well-scoped for the narrow domain of npm package release notes. Each tool earns its place, covering the essential workflow of discovering versions and retrieving release notes/breaking changes without redundancy.
The set covers the core lifecycle for the stated purpose: version discovery, breaking changes, and full changelog. A minor gap is that there is no direct way to get a single version's notes without specifying a 'from' version, but this can be worked around using list_versions and the between tools.