Skip to main content
Glama
JVMind MAT Heap Dump Analyzer

JVMind MAT Heap Dump Analyzer

Related Servers

Alternatives to JVMind MAT Heap Dump Analyzer

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Headless MCP server for Eclipse MAT that enables analyzing Java heap dumps using built-in commands, OQL queries, and predefined reports.
      6
      57 npm
      28
      Apache 2.0
    • A
      license
      D
      quality
      D
      maintenance
      MCP server that provides 8 tools for Java memory leak investigation: \- Class histograms, GC pressure snapshots, JFR recordings, heap dumps, MAT leak suspects analysis, async-profiler allocation profiles \- Structured confidence-based verdicts (none/low/medium/high) requiring independent signal corroboration \- Designed for use inside Claude Code with two slash commands
      8
      4
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for profiling Java applications via JDK utilities (jcmd, jfr, jps). Enables AI assistants to diagnose performance, analyze threads, and inspect JFR recordings without manual CLI usage.
      26
      64 npm
      10
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Hybrid TypeScript/Java MCP server for analyzing JVM Flight Recorder files, enabling AI agents to diagnose exceptions, slow SQL, network latency, and performance bottlenecks.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server for exploring, analyzing, and decompiling Java JAR files.
      570 npm
      9
      MIT

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct analysis artifact (histogram, dominator tree, top consumers, threads, thread locals, GC paths, OQL, connection pools), and descriptions explicitly cross-reference when to prefer a sibling tool (e.g. mat_histogram vs mat_top_consumers vs mat_dominator, mat_path2gc vs mat_dominator). Composite tools like mat_diagnose_oom are clearly framed as aggregations rather than duplicates.

    Naming Consistency4/5

    There is a readable two-tier convention: lifecycle tools use plain verb_noun (open_heapdump, get_heapdump_status, list_heapdumps, close_heapdump, dump_java_heap), and analysis tools are uniformly mat_-prefixed. Minor deviations like mat_threadlocals and mat_path2gc (digit abbreviation) break the pattern slightly.

    Tool Count4/5

    Nineteen tools is on the heavy side of the ideal range, but heap-dump analysis genuinely has many distinct report types plus a lifecycle group (open/status/list/close/live dump/process discovery). Little appears redundant, though a couple of composite tools (mat_diagnose_oom) could arguably be derived from primitives.

    Completeness5/5

    The surface covers the full lifecycle (discover processes, capture live dumps, open, poll status, list, close) and a broad analysis set (overview, histogram, dominator, top consumers, threads, thread locals, object inspection, GC paths, leak suspects, connection pools, SQL-in-threads, OQL). No obvious dead ends for typical OOM/leak investigations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues