Ext Ops Panel
Open dashboard
Comparison

WinDbg Pane vs io.github.daedalus/mcp-gdbserver

WinDbg Pane is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑30.

WinDbg Pane is a plugin bundle for AI coding tools published by glslang. No marketplace we read lists it any more. io.github.daedalus/mcp-gdbserver is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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

Where each is published
MarketplaceWinDbg Paneio.github.daedalus/mcp-gdbserver
Community marketplace glslang/windbg-mcp Removed on 2026-10-30
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 17
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 73
Downloads/week (PyPI): 23
Forks (GitHub): 0
Stars (GitHub): 0
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

WinDbg Pane vs io.github.daedalus/mcp-gdbserver
FactWinDbg Paneno longer listed · io.github.daedalus/mcp-gdbserver
Marketplaces that list it (differs)01
Stars (GitHub) (differs)170
Forks (GitHub) (differs)20
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-gdbserver)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/glslang/windbg-mcpgithub.com/daedalus/mcp-gdbserver
Changes in the last 7 days00
First seen (differs)2026-10-192026-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 WinDbg Pane

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • mcp-windbg-skills

    WinDbg skills for crash dump analysis, remote debugging, kernel debugging, and setup diagnostics.

    by Sven Scharmentke · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • windbg

    WinDbg diagnosis workflows and report validation for applications, services, UMDF/user-mode drivers, and kernel-mode drivers.

    by Microsoft · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • MCP Server for WinDbg Crash Analysis

    A Model Context Protocol server for Windows crash dump analysis using WinDbg/CDB

    by svnscha · MCP server

    Listed on: Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces · Describes nearly the same job

  • mcp-windbg-agents

    Crash-analyst agent for investigating Windows crash dumps and reporting findings.

    by Sven Scharmentke · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • windbg

    WinDbg diagnosis workflows for native Windows applications, services, UMDF/user-mode drivers, and kernel-mode drivers. Covers crashes, hangs, heap corruption, memory exhaustion…

    by microsoft · Plugin bundle

    Listed on: Copilot CLI: github/awesome-copilot · Describes nearly the same job

  • x64dbg MCP

    Windows x64dbg/x32dbg debugging with guarded sessions, breakpoints, memory and runtime evidence.

    by rison1337 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

WinDbg Pane

In its own words, on Community GitHub marketplaces:

A WinDbg-style pane that follows windbg-mcp tool calls: disassembly, registers, stack, memory, breakpoints and a command log.

io.github.daedalus/mcp-gdbserver

In its own words, on Official MCP Registry:

MCP server for remote debugging with gdbserver

How to run each

WinDbg Pane

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.daedalus/mcp-gdbserver As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-gdbserver -- uvx mcp-gdbserver

Commands 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

Neither one's marketplaces publish the settings it asks for.

What it can do: WinDbg Pane · What it can do: io.github.daedalus/mcp-gdbserver · 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.

Where the data comes from: how the catalog is built