Skip to main content
Glama
William-An

cpp-debug-mcp

by William-An
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cpp-debug-mcp

No user-submitted related servers found.

    Related Servers

    • LLDB MCP Server

      benpm
      A
      license
      A
      quality
      D
      maintenance
      Provides structured debugging capabilities through LLDB, enabling AI assistants to set breakpoints, inspect variables, analyze crashes, disassemble code, and evaluate expressions in C/C++ programs.
      17
      3
      Apache 2.0

    • MCP Debugger

      darknoon
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides debugging capabilities for Python, C, C++, Rust, Swift, and more through the Debug Adapter Protocol, enabling breakpoints, step-by-step evaluation, and stack traces.
      8 npm
      4
      MIT

    • lldb-mcp-server

      FYTJ
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes LLDB debugging capabilities, enabling AI-assisted interactive debugging of C/C++ applications through 40 specialized tools.
      4
      MIT

    • clangd-mcp-server

      felipeerias
      A
      license
      A
      quality
      F
      maintenance
      Provides C++ code intelligence tools for AI agents via the Model Context Protocol, enabling symbol navigation, type information, and diagnostics.
      9
      48
      Mozilla Public 2.0

    • gdbmcp

      luckinbyte
      A
      license
      Not graded
      quality
      D
      maintenance
      Attaches to a running C++ process and exposes tools to inspect live memory via a resident GDB subprocess, enabling LLMs to read fields, follow pointers, and access STL containers without modifying target code.
      MIT
    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

    A3.6/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with GDB and LSP tools separated by prefix, and combined tools like analyze_function and diagnose_crash_site uniquely bridging the two domains. No two tools are ambiguous in their function.

    Naming Consistency5/5

    All tools follow a consistent naming pattern: gdb_ for GDB operations, lsp_ for LSP operations, and descriptive names for combined tools. The pattern is predictable and aids agent understanding.

    Tool Count4/5

    27 tools is on the higher side, but the server covers two distinct domains (runtime debugging and static analysis), each with a reasonable set of operations. The count is justified by the comprehensive scope, though a slight reduction could improve focus.

    Completeness4/5

    The tool surface covers the full debugging lifecycle (session management, breakpoints, stepping, memory inspection, backtraces) and comprehensive LSP features (diagnostics, navigation, signature help). Minor missing features like watchpoints or program restart are present via raw commands, so no critical gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources