Skip to main content
Glama
uzhaoy

kd-mcp

by uzhaoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to kd-mcp

No user-submitted related servers found.

    Related Servers

    • winrm-mcp

      uzhaoy
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling a Windows guest VM over WinRM, enabling PowerShell/CMD execution, file transfer, reboot, and KDNET debug configuration, typically paired with kd-mcp.
      12
      MIT

    • Aragorn

      alfarom256
      A
      license
      Not graded
      quality
      D
      maintenance
      A direct kernel debugger MCP server for Windows security research that connects to VM kernels via kdnet using DbgEng COM interfaces. It exposes over 60 tools for memory inspection, breakpoint management, and coordinated execution control between the host and target VM.
      3
      Do What The F*ck You Want To Public

    • windbg-mcp

      kanren3
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that drives cdb.exe/kd.exe to provide WinDbg debugging to LLM agents, enabling crash dump analysis, live process debugging, kernel debugging, and a searchable command reference.
      9 npm
      5
      MIT

    • CDB-MCP

      cc682
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to perform live debugging, dump analysis, and remote debugging by exposing Microsoft CDB capabilities through MCP. It manages cdb.exe sessions, forwards commands, and returns raw debugger output.
      7
      MIT

    • windbg_mcp

      276793422
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes WinDbg/cdb as a session-based debugging tool, allowing users to open dumps, launch/attach processes, and execute arbitrary cdb commands with persistent context across commands.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes. The two start tools (start_from_state and start_kd) could be confused but are differentiated by their descriptions (state file vs explicit params). All others are clearly distinct.

    Naming Consistency3/5

    Naming convention is mixed: some verb_noun (list_sessions, read_output, start_kd, stop_kd), others follow different patterns (break_in, continue_go, health_check, kd_command). This inconsistency may confuse an agent expecting a uniform pattern.

    Tool Count4/5

    9 tools is a reasonable count for a KD session manager. It covers starting, stopping, sending commands, reading output, and session listing without being excessive or too sparse.

    Completeness4/5

    The tool set covers the core lifecycle of KD sessions: start, stop, interact (break, continue, command), and monitor (list, read, health). Missing advanced debugging features, but those are beyond the server's stated scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources