Skip to main content
Glama
mcp-jvm-diagnostics

mcp-jvm-diagnostics

by Dmitriusan

Related Servers

Alternatives to mcp-jvm-diagnostics

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to obtain deterministic, structured JVM production diagnostics—including deadlocks, hot locks, bottleneck frames, and planned GC/heap analysis—from thread dumps, GC logs, and heap histograms without hallucinating from raw logs.
      4
      50 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to review and compare Go goroutine dumps, surfacing goroutine leaks, lock pile-ups, exhausted database pools, and missing HTTP timeouts from dump text alone without connecting to the service.
      387 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents diagnose and debug live Java applications by auto-discovering JVMs and attaching Arthas to run diagnostic commands like thread, trace, watch, and ognl.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Live .NET runtime diagnostics for AI assistants. Ask Claude to diagnose memory leaks, GC pressure, LOH fragmentation, and thread starvation in any running .NET process — no code changes required.
      7
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables analysis of JVM thread dumps to detect deadlocks, CPU spikes, pool exhaustion, and virtual thread pinning, returning a health score and interactive report link.
      2
      82 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to debug Java applications using JDB, supporting breakpoints, stepping, expression evaluation, thread analysis, and more.
      4
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct JVM diagnostic source or operation (JFR, thread dumps, GC logs, heap histograms, comparison, reporting, unified diagnosis), with no functional overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., analyze_jfr, generate_report, diagnose_jvm), making the toolset predictable and easy to navigate.

    Tool Count5/5

    With 7 tools, the server covers the major diagnostic areas (JFR, thread dumps, GC logs, heap histograms, plus comparison and unified analysis) without being bloated or sparse.

    Completeness4/5

    The tool surface covers the core diagnostic workflows, but lacks explicit CPU profiling or memory leak tools beyond heap histograms; still, the set is largely complete for general JVM diagnostics.