Skip to main content
Glama

Related Servers

Alternatives to debug-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An intelligent debugging assistant that automates the debugging process by analyzing bugs, injecting HTTP-based debug logs into code across multiple environments (browser, Node.js, mobile, etc.), and iteratively fixing issues based on real-time feedback.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides intelligent error detection and debugging capabilities across multiple programming languages with real-time monitoring of build, lint, runtime, console, and test errors. Offers AI-enhanced error analysis with automated resolution suggestions and context-aware debugging.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding tools with a shared knowledge base of real-world fixes and gotchas, verified by usage, to stop debugging errors others already solved.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query runtime debugging facts (stack traces, logs, function arguments) captured by Syncause, allowing them to fix root causes with evidence instead of guessing.
      4 npm
      1
      -

    TDQS

    C2.7/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: case memory operations vs. code inspection vs. reporting. The main ambiguity is between search_code and grep (both search code) and between search_case and list_cases, though descriptions partially clarify the differences.

    Naming Consistency4/5

    The vast majority follow a consistent snake_case verb_noun pattern (search_case, list_cases, delete_case, read_file, check_syntax). The exceptions are 'grep' and 'debug', which are bare verbs and break the pattern, but the overall convention is strong.

    Tool Count3/5

    At 18 tools, the set sits in the borderline-heavy range. The count is justified somewhat by spanning case memory, code analysis, and reporting, but it still feels more expansive than a typical debug tool requires.

    Completeness4/5

    The case memory lifecycle is well covered (create via debug, read, search, list, delete, mark effectiveness) and code inspection is solid. Minor gaps exist, such as no way to manually add or edit a case, and no direct code modification, but these are workable for the stated debugging purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues