Breaking Changes & Migration Data

io.github.nigelcox98Published by GitHub account nigelcox98v0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant look up what breaks when upgrading a software package and what to use instead, based on official documentation.

What you can do
This remote MCP server provides migration and breaking-change information for software packages. According to its registry description, it answers what breaks when you upgrade a package and what to use instead, drawing on official documentation. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to plan or explain a dependency upgrade and wants to know which APIs or behaviors changed and what replacements exist. It is aimed at upgrade and migration questions rather than general coding help.
Requirements
It runs as a remote streamable HTTP endpoint, so no local runtime or package installation is needed. The manifest declares no authentication, environment variables, or headers, and no account or API key is required.
Before you install
The endpoint is third-party and hosted remotely, so queries are sent to that service; avoid including confidential code or identifiers in prompts. The manifest declares no credentials, and no tool list is published, so the exact data handling and behavior cannot be verified from the provided information.

Installation

In SourceWeft

  1. Open Breaking Changes & Migration Data in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nigelcox98%2Fbreaking-changes/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "breaking-changes-migration-data": {
      "type": "http",
      "url": "https://agentdataapi.onrender.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

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.

Takes no parameters.

get_breaking_changes

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.

Parameterspackagerequiredversion

check_upgrade_safety

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.

Parameterspackagerequiredtarget_versionrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.