dep-diff-mcp
Analyzes Dependabot pull requests to provide human-readable upgrade plans with risk assessment, breaking changes, security fixes, and migration guidance
Fetches release notes from GitHub repositories to extract breaking changes and migration guide links for package upgrades
Analyzes npm package version changes to provide semver classification, security fixes, and upgrade recommendations
Analyzes PyPI package version changes to provide semver classification, security fixes, and upgrade recommendations
dep-diff-mcp
MCP server that translates a lockfile diff into a human-readable upgrade plan.
Point your AI assistant (Cursor, Claude Desktop, Claude Code) at a Dependabot PR, npm outdated output, or any pair of package versions, and get back a ranked upgrade plan: semver class, breaking changes pulled from GitHub release notes, CVEs fixed in the range, migration guide links, and a clear recommendation per package.
Install
Claude Code
One command, user scope (available in every project):
claude mcp add -s user dep-diff -- npx -y @digicatalyst/dep-diff-mcpProject scope (writes .mcp.json at repo root, team-shared):
claude mcp add -s project dep-diff -- npx -y @digicatalyst/dep-diff-mcpWith an explicit token (skip this if you have the gh CLI authenticated — see GitHub token below):
claude mcp add -s user --env GITHUB_TOKEN=ghp_xxx dep-diff -- npx -y @digicatalyst/dep-diff-mcpVerify:
claude mcp listRestart the Claude Code session to pick up the server.
Cursor and Claude Desktop
Add to your MCP client config:
Cursor:
~/.cursor/mcp.jsonClaude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows)
{
"mcpServers": {
"dep-diff": {
"command": "npx",
"args": ["-y", "@digicatalyst/dep-diff-mcp"]
}
}
}Restart your MCP client. Ask something like "what's risky in this Dependabot PR?" and the tools are invoked automatically.
Related MCP server: upgrade-pilot-mcp
GitHub token (optional but recommended)
The server hits the GitHub API to read release notes. Without a token you get 60 requests per hour (GitHub's anonymous limit) — enough for occasional single-package queries, not enough for bulk lockfile analysis.
The server resolves a token in this order:
GITHUB_TOKENenvironment variable, if set.gh auth token— if the GitHub CLI is installed and authenticated, the server uses that token automatically. No config change needed.Anonymous (60 req/hr).
Recommended: use the gh CLI
If you already have gh installed (brew install gh && gh auth login), stop here — the server picks up your existing auth. No plaintext token anywhere.
Alternative: environment variable
Create a fine-grained token at https://github.com/settings/tokens:
Token name:
dep-diff-mcpExpiration: 90 days (rotate periodically)
Repository access:
Public Repositories (read-only)— no private repo accessPermissions: none beyond the default public read — do not grant
repo,workflow,user, or any write scope
Then reference it in the MCP config:
{
"mcpServers": {
"dep-diff": {
"command": "npx",
"args": ["-y", "@digicatalyst/dep-diff-mcp"],
"env": { "GITHUB_TOKEN": "github_pat_xxx" }
}
}
}Security notes
This config file lives on your disk in plaintext. Keep perms tight (
chmod 600) and do not paste the token into AI chats, issues, or shared screens — transcripts are often retained.The token in this config should be least-privilege (public repo read only). Even leaked, it can only read public data you could already read.
Rotate tokens periodically. Revoke any token that may have been exposed at https://github.com/settings/tokens.
The server never writes the token to stdout/stderr or the response payload.
Tools
analyze_package_change
Analyze one package upgrade. Inputs: ecosystem (npm or pypi), name, fromVersion, toVersion.
analyze_packages_bulk
Analyze up to 50 package upgrades in parallel. Returns packages ranked by risk (security > caution > review > likely-safe > safe), plus summary counts.
What you get back
Semver classification — major / minor / patch / downgrade / unknown
Breaking changes — extracted from GitHub release notes headers
Security fixes — CVEs present at
fromVersionbut resolved attoVersion(via OSV.dev)Migration links — upgrade guide URLs found in release notes
Recommendation — single-line verdict + level
Supported ecosystems
npm
PyPI
Development
npm install
npm run build
GITHUB_TOKEN=ghp_xxx npm run inspect # MCP InspectorLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceAI-powered dependency vulnerability and breaking change analyzer that scans dependencies, identifies vulnerabilities via OSV.dev, and uses AI to assess real impact and suggest fixes.Last updatedApache 2.0
- Alicense-qualityDmaintenanceEnables AI agents to safely upgrade JavaScript and TypeScript projects through dependency analysis, upgrade path detection, breaking change identification, codemod application, and PR summary generation.Last updated20MIT
- AlicenseAqualityBmaintenanceAnalyzes database migrations for risks like lock contention and data loss before they run. Supports Flyway and Liquibase formats, providing risk scores and rollback generation.Last updated628MIT
- Flicense-qualityBmaintenanceProvides breaking changes analysis for libraries across multiple languages, enabling version upgrade planning, dependency audits, and migration reports through MCP tool access and expert workflows.Last updated
Related MCP Connectors
Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Supply chain risk scoring for npm, PyPI, Cargo, and Go. 9 tools. Behavioral signals.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DigiCatalyst-Systems/dep-diff-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server