Skip to main content
Glama
cc682

CDB-MCP

by cc682
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CDB-MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      21 npm
      5
      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.
      -

    • GDB MCP Server

      yywz1999
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with GDB for debugging via the MCP protocol. Supports setting breakpoints, stepping through code, inspecting memory and registers, and more.
      86
      MIT

    • MCP Debug Server

      nickzer0
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for debugging Windows processes using WinDbg and CDB. It enables users to attach to processes, manage breakpoints, inspect memory, and control execution flow through natural language.
      2
      -
    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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: session lifecycle (create/close/list), command execution, output polling, waiting, and interrupting. Even the similar get_output and wait_for_prompt are differentiated by their descriptions (reading buffer vs. waiting for prompt), leaving no real ambiguity.

    Naming Consistency4/5

    Names mostly follow a verb_noun pattern (create_session, close_session, list_sessions, get_output), with a few bare verbs (execute, interrupt) that still clearly indicate actions. The style is consistent and readable, with only minor deviation from the noun suffix.

    Tool Count5/5

    Seven tools is well-scoped for a debugger integration. Each tool covers a necessary aspect of session and command management without redundancy, and the count is appropriate for the complexity of CDB interaction.

    Completeness5/5

    The tool set covers the full debug session lifecycle: create, close, list, execute arbitrary commands, and handle asynchronous output (poll, wait, interrupt). There are no obvious dead ends—any CDB command can be run, and pending operations can be managed. The only theoretical gap (dedicated breakpoint tools) is handled by the generic execute tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources