JVM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARTHAS_SSH_HOST | No | Remote host to connect to (format: user@remote-host) | |
| ARTHAS_SSH_PORT | No | SSH port for the remote connection | 22 |
| ARTHAS_SSH_PASSWORD | No | Password for SSH authentication if using password authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_java_processesA | 列出所有Java进程 |
| get_thread_infoA | 获取指定进程的线程信息 |
| get_jvm_infoA | 获取JVM基础信息 |
| get_memory_infoA | 获取内存使用情况 |
| get_stack_traceA | 获取线程堆栈信息 |
| get_class_infoB | 获取类信息 - 使用jmap -histo和javap命令获取完整的类信息 |
| get_jvm_statusB | 获取JVM整体状态报告 |
| get_stack_trace_by_methodB | 获取方法的调用路径 |
| decompile_classB | 反编译指定类的源码 |
| search_methodC | 查看类的方法信息 |
| watch_methodC | 监控方法的调用情况 |
| get_logger_infoC | 获取logger信息 |
| set_logger_levelC | 设置logger级别 |
| get_dashboardC | 获取系统实时数据面板 |
| get_jcmd_outputB | 执行 jcmd 子命令 |
| get_jstat_outputA | 执行 jstat 监控命令 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools have distinct purposes targeting specific JVM diagnostics (e.g., get_memory_info vs. get_thread_info), but some overlap exists: get_class_info and search_method both retrieve class/method details, and get_stack_trace and get_stack_trace_by_method both handle stack traces, which could cause confusion. However, their descriptions clarify the differences.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_jvm_info, list_java_processes, set_logger_level). There are no deviations in naming conventions, making the set predictable and easy to parse.
With 16 tools, the count is slightly high but reasonable for a JVM diagnostics server covering processes, memory, threads, classes, and logging. It avoids being excessive (under 25) and provides comprehensive coverage, though some tools could potentially be consolidated.
The toolset covers core JVM diagnostics well: process listing, memory, threads, class inspection, and logging. However, there are notable gaps: several tools are marked as '暂未实现' (not yet implemented), including key ones like decompile_class and get_dashboard, which limits functionality. Additionally, there's no tool for modifying JVM settings beyond logger levels.