analyze_package_change — dep diff mcp MCP Tool
analyze_package_change
(analyze package change) is one of 2 tools on the
dep diff mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_package_change from your client
- Claude Code dep diff mcp analyze_package_change run in your project directory
- Claude Desktop dep diff mcp analyze_package_change ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor dep diff mcp analyze_package_change ~/.cursor/mcp.json
- VS Code dep diff mcp analyze_package_change .vscode/mcp.json
- Zed dep diff mcp analyze_package_change ~/.config/zed/settings.json
- Windsurf dep diff mcp analyze_package_change ~/.codeium/windsurf/mcp_config.json
- Cline dep diff mcp analyze_package_change ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI dep diff mcp analyze_package_change ~/.gemini/settings.json
- Grok dep diff mcp analyze_package_change .mcp.json (in your project root)
- ChatGPT dep diff mcp analyze_package_change Settings → Connectors → Advanced → Developer mode
- Claude.ai dep diff mcp analyze_package_change Settings → Connectors → Add custom connector
- LangChain dep diff mcp analyze_package_change pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dep-diff-mcp https://dep-diff.digicatalyst.ca/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.