breaking-changes-mcp
Related Servers
Alternatives to breaking-changes-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides structured migration briefs for LLM coding agents covering breaking changes, codemod coverage, and hallucination warnings for major version bumps of packages like tailwindcss, next, and react.-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to verify, compare, and safely upgrade npm packages by scoring packages from public signals and sandboxed co-installation, detecting breaking API surface changes, and rewriting code that upgrades break.44 npm8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to identify exactly what broke between two dependency versions, with citations for every claim, and to verify package existence to catch typosquatting, all without requiring an API key.MIT
- AlicenseAqualityAmaintenanceEnables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.5MIT
- AlicenseNot gradedqualityBmaintenanceVerified, dated facts for AI coding agents: what breaks between npm package versions (diffed from TypeScript types), per-version vulnerabilities, the newest version compatible with a given Node/Python/Rust/PHP, end-of-life dates of ~480 runtimes and frameworks, and AI model prices. Covers npm, PyPI, crates.io and Packagist.1AGPL 3.0
- AlicenseAqualityCmaintenanceBreaking-change diffs for npm packages, served over REST and MCP, so coding agents stop writing code against outdated API knowledge.2Functional Source , Version 1.1, MIT Future
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.