Vdiff MCP Server

Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes.

Local serverstdioTypeScript

What is the Vdiff MCP server?

Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes. Exposed over MCP by the vdiff mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A breaking-change diff API for npm packages. Given a package and two versions, it returns a structured, machine-readable list of what actually broke: removed exports, changed function signatures, and removed or changed class and interface members. Each entry includes the before and after signatures plus a short migration note.

Its toolset

Everything the assistant can do here goes through one of these:

  • Endpoint — Purpose
  • Configuration — The Configuration tool exposed by this server

Configuration

You will need one environment variable: DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at vdiff-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vdiff's toolset — Endpoint, Configuration — is a fair guide to whether it matches your workflow. It is maintained by mcurmi05; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Vdiff's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the vdiff mcp server does with a few real requests.

Available tools

ToolWhat it does
EndpointPurpose
ConfigurationThe Configuration tool exposed by this server.

How to install the Vdiff MCP server

{
  "mcpServers": {
    "vdiff": {
      "command": "npx",
      "args": ["-y", "vdiff-mcp"],
      "env": {
        "DATABASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
DATABASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Vdiff to Endpoint.
  • Use Vdiff to Configuration.

Frequently asked questions

It connects Vdiff to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Endpoint, Configuration) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Vdiff directly.