MCP server for JVM diagnostics — analyze thread dumps, detect deadlocks, parse GC logs, and get JVM tuning recommendations
MCP server for JVM diagnostics — analyze thread dumps, detect deadlocks, parse GC logs, and get JVM tuning recommendations. That is what the mcp jvm diagnostics mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
A Model Context Protocol (MCP) server that gives AI assistants the ability to analyze JVM thread dumps and GC logs. It detects deadlocks, identifies lock contention hotspots, analyzes garbage collection pressure, and recommends JVM tuning parameters.
The server publishes 5 tools. What each one is for:
analyze_thread_dump — Parse a JVM thread dump and analyze thread states, detect deadlocks, and identify lock contentionanalyze_gc_log — Parse a GC log and analyze garbage collection patterns, pause times, and memory pressureanalyze_heap_histo — Parse jmap -histo output and detect memory leak candidates, object creation hotspots, and classloader leaksdiagnose_jvm — Unified JVM diagnosis combining thread dump and GC log analysis for comprehensive root cause analysiscompare_heap_histos — Compare two jmap -histo snapshots taken at different times to detect memory growth patterns and leak candidatesThe server ships on npm as mcp-jvm-diagnostics, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Jvm Diagnostics's toolset — analyze_thread_dump, analyze_gc_log, analyze_heap_histo and 2 more — is a fair guide to whether it matches your workflow. It is maintained by dmitriusan; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Jvm Diagnostics's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| analyze_thread_dump | Parse a JVM thread dump and analyze thread states, detect deadlocks, and identify lock contention. |
| analyze_gc_log | Parse a GC log and analyze garbage collection patterns, pause times, and memory pressure. |
| analyze_heap_histo | Parse jmap -histo output and detect memory leak candidates, object creation hotspots, and classloader leaks. |
| diagnose_jvm | Unified JVM diagnosis combining thread dump and GC log analysis for comprehensive root cause analysis. |
| compare_heap_histos | Compare two jmap -histo snapshots taken at different times to detect memory growth patterns and leak candidates. |
{
"mcpServers": {
"jvm-diagnostics": {
"command": "npx",
"args": ["-y", "mcp-jvm-diagnostics"]
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.