mcp-jvm-diagnostics
Related Servers
Alternatives to mcp-jvm-diagnostics
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.450 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets 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.4MIT
- AlicenseAqualityCmaintenanceLive .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.72MIT
- AlicenseAqualityCmaintenanceEnables analysis of JVM thread dumps to detect deadlocks, CPU spikes, pool exhaustion, and virtual thread pinning, returning a health score and interactive report link.282 npmMIT

karellen-jdb-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables LLMs to debug Java applications using JDB, supporting breakpoints, stepping, expression evaluation, thread analysis, and more.4Apache 2.0
TDQS
Scored across 7 tools
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.
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.
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.
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.