JVM Diagnostics MCP

Name: JVM Diagnostics MCP
Author: brunoborges

@brunoborges

リポジトリ

JVM Diagnostics MCP について

MCP Server for starting new projects

#java #jvm #diagnostics #mcp #server

基本情報

カテゴリ

開発者ツール

ライセンス

MIT license

ランタイム

java

トランスポート

stdio

公開者

brunoborges

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "jvm-diagnostics": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "JAVA_HOME",
        "ghcr.io/brunoborges/jvm-diagnostics-mcp:latest"
      ],
      "env": {
        "JAVA_HOME": "/path/to/java/home"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is JVM Diagnostics MCP?

JVM Diagnostics MCP is an MCP server that wraps various JVM diagnostic command-line tools (jstat, jcmd, jps) and exposes them through a prompt-enhanced interface. It is intended for developers and operations personnel who need to monitor and diagnose JVM processes locally.

How to use JVM Diagnostics MCP?

Install by downloading the JAR from the GitHub release page and configuring the server in Claude Desktop or VS Code Insiders, or run it inside a Docker container. The server operates via stdio transport and requires Java 17+ (or Docker) with JVM diagnostic tools available in the environment.

Key features of JVM Diagnostics MCP

Wraps jstat, jcmd, and jps diagnostic tools
Adds a prompt to improve tool interaction with LLMs
Monitors JVM performance metrics
Inspects and manages JVM processes
Analyzes thread dumps, heap dumps, and other diagnostics

Use cases of JVM Diagnostics MCP

Monitoring live JVM performance metrics using jstat
Listing and inspecting running Java processes with jps
Executing diagnostic commands on a JVM via jcmd
Capturing and analyzing thread dumps and heap dumps

FAQ from JVM Diagnostics MCP

What does JVM Diagnostics MCP do?

It wraps JVM command-line diagnostics tools (jstat, jcmd, jps) and exposes them as MCP tools with an enhanced prompt, enabling an LLM to run JVM diagnostics interactively.

Is it safe to use?

The README advises caution because the server is LLM-driven; users should validate generated commands. The software is provided “as is” without warranty, and you use it at your own risk.

Is it secured and should I run it on a remote server?

No. The server uses only the stdio transport and is intended to run locally on your machine. It is not secured and could be exploited if accessible remotely.

How do I install JVM Diagnostics MCP?

You can run it as a Java application (requires Java 17+) by downloading the JAR from the GitHub release page, or run it inside a Docker container. Configuration examples for Claude Desktop and VS Code Insiders are provided in the README.

What are the runtime dependencies?

Java 17 or higher is required, and JVM diagnostic tools (jstat, jcmd, jps) must be available in the environment. Docker is an alternative runtime if Java is not installed locally.