Breaking Changes & Migration Data

What breaks when you upgrade a package, and what to use instead - from official docs.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
60%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~379Tokens (tool definitions)
~765 BTypical response size
Minimal attention impact (0.30% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "breaking-changes": {
      "url": "https://agentdataapi.onrender.com/mcp"
    }
  }
}

Remote endpoints

https://agentdataapi.onrender.com/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡list_packages

List every package with breaking-change data available, including tracked versions and how many breaking changes each has. Call this first if you are unsure whether a package is covered.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "list_packagesArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "list_packagesDictOutput"
}
🟢get_breaking_changes(package, version)

Get breaking changes for a package upgrade: removed APIs with their replacements and the reason for each, changed defaults, behavior changes, known incompatible dependencies, official source URL, and codemod/automated-fix commands. Omit `version` to get every tracked version. Use this instead of relying on training data, which may predate the release.

Input Schema

{
  "type": "object",
  "properties": {
    "package": {
      "title": "Package",
      "type": "string"
    },
    "version": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Version"
    }
  },
  "required": [
    "package"
  ],
  "title": "get_breaking_changesArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "get_breaking_changesDictOutput"
}
🟢check_upgrade_safety(package, target_version)

Given a package and the version you are upgrading TO, return a concise checklist an agent can act on: the count of breaking changes, the highest-risk removals, whether automated codemods exist, and the recommended upgrade path. Use before performing an upgrade.

Input Schema

{
  "type": "object",
  "properties": {
    "package": {
      "title": "Package",
      "type": "string"
    },
    "target_version": {
      "title": "Target Version",
      "type": "string"
    }
  },
  "required": [
    "package",
    "target_version"
  ],
  "title": "check_upgrade_safetyArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "check_upgrade_safetyDictOutput"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools