Skip to main content
Glama
Sign In
ej-technologies

JProfiler

by ej-technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to JProfiler

Related Servers

  • javaperf

    theSharque
    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
    40 npm
    10
    MIT

  • arthas-mcp

    x0c
    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.
    3
    MIT

  • arthas-mcp

    HeavenC
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that connects AI agents to live Java processes via Alibaba Arthas, enabling real-time diagnostics, debugging, and performance analysis without code changes.
    25
    MIT

  • sleuths-mcp

    threshbyte
    A
    license
    A
    quality
    B
    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
    317 npm
    MIT

  • mcp-dotnet-diagnostics

    aayushmdesai
    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
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target distinct stages of the profiling workflow: discovery, session start, attachment, status, heap dump, snapshot loading, and querying. There is some overlap between check_status and attached_action around controlling recording, and between create_heap_dump and attached_action's heap-dump actions, but the descriptions make the intended boundaries reasonably clear.

Naming Consistency3/5

The set is mostly snake_case, with verb_noun names such as prepare_profiling, load_snapshot, check_status, create_heap_dump, and list_jvms. However, query and attach are bare verbs, and attached_action is an adjective_noun form rather than an imperative verb, so the convention is readable but not fully consistent.

Tool Count5/5

Eight tools is well scoped for a JVM profiling server: each covers a distinct part of the lifecycle from discovering JVMs to recording, loading snapshots, and querying results. There are no obviously redundant tools or missing slots that would suggest the count is off.

Completeness5/5

The surface covers the full expected workflow: list_jvms for discovery, prepare_profiling and attach for starting sessions, check_status and attached_action for control, create_heap_dump for heap capture, load_snapshot for existing files, and query for analysis. No major lifecycle operation appears to be missing.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources