dep-diff-mcp

Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.

Community: Submitted by a user or imported; check the owner before granting accessDegradedNo sign-inGlobalFreeRead-only

What it can do

  • Analyze Package Change: Given one package and two versions (from -> to), returns a structured upgrade analysis: semver classification, GitHub release notes summary, detected breaking changes, security
  • Analyze Packages Bulk: Analyzes a list of package upgrades in parallel and returns a unified risk report with packages ranked by recommendation level (security > caution > review > likely-safe > safe)

What data it sees

Do you need an account

No: the server works without sign-in

Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions. Point this MCP at a Dependabot PR, lockfile diff, or any pair of package versions and get back a ranked upgrade plan. For every dependency bump it returns semver classification, breaking changes extracted from GitHub release notes, CVEs fixed in the range (via OSV.dev), migration guide links, and a per-package recommendation. Bulk tool analyzes up to 50 package changes in parallel and ranks by risk level (security > caution > review > likely-safe > safe). Supports npm, PyPI, and GitHub Actions (pass the action reference as the name, e.g. actions/checkout).

How to connect

How to connect dep-diff-mcp to Claude

The server address to paste into Claude settings:

https://dep-diff-mcp--digicatalyst-systems.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect dep-diff-mcp to ChatGPT

The server address to paste into ChatGPT settings:

https://dep-diff-mcp--digicatalyst-systems.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect dep-diff-mcp to Cursor

The server address to paste into Cursor settings:

https://dep-diff-mcp--digicatalyst-systems.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (2)

Raw names from tools/list. Only developers need these.

analyze_package_changeGiven one package and two versions (from -> to), returns a structured upgrade analysis: semver classification, GitHub release notes summary, detected breaking changes, security advisories fixed in the range, migration guide links, and a clear recommendation. Use when the user asks about a specific package upgrade. Supports npm, pypi, and github-actions (use the action reference as the name, e.g. actions/checkout). For analyzing many packages at once, use analyze_packages_bulk instead.
analyze_packages_bulkAnalyzes a list of package upgrades in parallel and returns a unified risk report with packages ranked by recommendation level (security > caution > review > likely-safe > safe). Use when the user provides many dependency changes from a Dependabot PR, npm outdated output, lockfile diff, or batch upgrade. Returns: total count, breakdown by semver class, total security fixes found, packages with breaking changes, and per-package details. Limit 50 packages per call.