BumpGuard MCP Server

Reports which of your code's API usages break before you upgrade a dependency (Python + .NET). Exposed over MCP by the bumpguard mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

It does this by static analysis only. BumpGuard never imports or executes third‑party code; it reads a package's real public API straight from its source.

• The model writes pydantic.BaseSettings or openai.ChatCompletion.create(...) — perfectly valid two versions ago, gone in the version you have installed
• You bump pandas from 1.5 to 2.2 and discover the breakage one stack trace at a time
• A changelog lists 1,800 breaking changes; you only care about the three your code actually touches

Adding it to your client

bumpguard-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

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

• Releasing — Releases are automated via GitHub Actions. To cut a release:

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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the bumpguard mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. BumpGuard's toolset — Releasing — is a fair guide to whether it matches your workflow. It is maintained by appcreationsca; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.