mcp-debugger vs Qwen DAP MCP
mcp-debugger is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
mcp-debugger is a plugin bundle for AI coding tools published by bherbruck. No marketplace we read lists it any more. Qwen DAP MCP is an MCP server published by SLP-DEV1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Qwen DAP MCP | |
|---|---|---|
| Community marketplace bherbruck/mcp-debugger | Removed on 2026-10-17 Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.18.2 Downloads/month (npm): 898 Downloads/week (npm): 122 Forks (GitHub): 0 (last published figure) Stars (GitHub): 3 (last published figure) Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | mcp-debuggerno longer listed · | Qwen DAP MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 3 (last published figure) |
| Forks (GitHub) (differs) | 0 | 0 (last published figure) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@slp-dev1/qwen-dap-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/bherbruck/mcp-debugger | github.com/slp-dev1/qwen-dap-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of mcp-debugger
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
debugium io.github.Algiras/debugium
AI-driven live debugger with MCP bridge for Python, JS, TS, Rust, Java, C/C++
-
aidb io.github.ai-debugger-inc/aidb
Debug any supported language with breakpoints, variable/state inspection, and stepping.
-
PyCharm-like Python debugging with breakpoints, stepping, variable inspection, and stack navigation
-
Interactively debug source code — set breakpoints, step through execution, inspect live variables, evaluate expressions, and trace root causes.
-
mcp-debugger io.github.Digital-Defiance/mcp-debugger
Node.js and TypeScript debugging with 25+ tools for AI agents
-
x64dbg io.github.bromoket/x64dbg
MCP server for x64dbg debugger - 23 mega-tools for AI-powered reverse engineering and debugging
What each says it does
mcp-debugger
Multi-language debugging via DAP - debug Python, JavaScript/TypeScript, Go, and Rust
Qwen DAP MCP
Native runtime debugging via DAP-to-MCP for crashes, hangs, dumps, symbols, and forensics.
How to run each
mcp-debugger
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Qwen DAP MCP As a local MCP server: npm package
claude mcp add --transport stdio qwen-dap-mcp -- npx -y @slp-dev1/qwen-dap-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Qwen DAP MCP publish no settings it asks for, so we do not compare settings.
What it can do: mcp-debugger · What it can do: Qwen DAP MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.