Skip to content

Release 0.25.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Sep 00:05
· 65 commits to main since this release
v0.25.0
c44ea94
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

🎉 Release 0.25.0

[0.25.0] - 2026-09-29

Highlights

  • Rust and C/C++ debugging work out of the box everywhere npm installs — CodeLLDB now ships as five per-platform packages (@debugmcp/codelldb-*) that npm installs as optional dependencies, and the CLI tarball shrinks from about 54 MB to a few MB (#383)
  • COBOL debugging, the ninth language — GnuCOBOL programs debug with COBOL-shaped variables, PERFORM-aware stepping, paragraph and section breakpoints, and attach by PID (#759)
  • mcp-debugger doctor — one command reports every language's runtime and debugger toolchain, with install hints (#423)
  • Kubernetes debugging recipe — port-forward and ephemeral-sidecar examples, registry-free manifests and per-language attach presets, verified weekly on kind (#424, #451)
  • The HTTP transport is locked down by default — it binds 127.0.0.1 and validates Host and Origin; --bind and --allowed-host open it deliberately for containers and remote clients (#667, #671, #677, #680)
  • Launches say how they ended — a launch that runs to completion names its exit code and the breakpoints that never hit, and a launch with nothing armed to stop it answers pending after 5 s instead of waiting out the 30 s ceiling (#701, #815)
  • Exit codes for Go and for JavaScript in Docker (#753, #796)
  • Breakpoint records match what the debugger said — a refused re-send leaves the adapter's own answer on the breakpoints, JavaScript breakpoints that fired are reported bound, and breakpoints can be set between runs for restart_debugging (#754, #673, #806)
  • JavaScript launches honour their options — adapterLaunchConfig keys pass through with feedback on what was used, stopOnEntry and environment removals work, and compiled TypeScript stops in its source view (#684, #703, #709, #791, #792)
  • Lighter startup — transports and adapters load lazily and the startup reapers are bounded: a freshly started stdio server drops from 287 MB to 190 MB (#395, #407–#411)
  • pi package — pi install npm:@debugmcp/mcp-debugger registers the server and the debugging skill (#714)
  • Signed everywhere — the Docker image and the PyPI launcher now carry build attestations, like the npm tarballs (#430)

This release has 180 changelog entries, too many for a release page. The full list is in CHANGELOG.md.

📦 Installation

Docker:

docker pull debugmcp/mcp-debugger:0.25.0

npm (global install):

npm install -g @debugmcp/mcp-debugger@0.25.0

npx (no install):

npx @debugmcp/mcp-debugger@0.25.0 stdio

PyPI:

pip install debug-mcp-server-launcher==0.25.0

Optional adapters (for programmatic embedding; the CLI above bundles all of them):

npm install @debugmcp/adapter-python   # or: adapter-ruby, adapter-javascript,
                                       # adapter-go, adapter-java, adapter-dotnet,
                                       # adapter-mock

🔏 Verify this release

gh attestation verify <asset>.tgz --repo debugmcp/mcp-debugger
gh attestation verify oci://index.docker.io/debugmcp/mcp-debugger:0.25.0 --repo debugmcp/mcp-debugger
npm audit signatures   # in a project that installs @debugmcp packages

The PyPI launcher carries PEP 740 attestations — see the "Verified details" on its PyPI page.
SBOMs (SPDX + CycloneDX) are attached as release assets.

📚 Documentation

See the README for usage instructions.

Assets 20
Loading