Skillget

jolokia-mcp-server

mcp
Guvenlik Denetimi
Gecti
Health Gecti
  • License — License: Apache-2.0
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 16 GitHub stars
Code Gecti
  • Code scan — Scanned 2 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose
This tool acts as an MCP server that connects Large Language Models (LLMs) directly to your Java application's internal management API. It allows the AI to read and modify Java Management Extensions (JMX) attributes and execute operations on MBeans via Jolokia.

Security Assessment
Overall Risk: High. While the automated code scan found no hardcoded secrets, dangerous patterns, or requested malicious permissions, the fundamental design of the tool carries significant risk. It opens a direct channel for an AI to modify application attributes and execute internal operations, which could easily lead to system instability or unauthorized configuration changes if the LLM is given a dangerous prompt. Furthermore, the JVM Agent distribution exposes an HTTP port directly from your application, expanding the attack surface and requiring strict network isolation.

Quality Assessment
The project appears to be in good health and actively maintained. It utilizes the permissive Apache-2.0 license, has a clear description, and shows recent repository activity (pushed within the last day). While it is a niche tool with a small community of 16 GitHub stars, it is backed by CI testing via GitHub Actions, indicating a baseline of development professionalism.

Verdict
Use with caution: while the code itself is safe, granting an LLM direct read and write access to your Java application's internal MBeans requires strict oversight, network isolation, and sandboxing to prevent accidental or malicious system disruption.
SUMMARY

Let LLMs manage your Java application via JMX/Jolokia 🌶️

README.md

Jolokia MCP Server

Test

MCP server for Jolokia, a JMX-HTTP bridge for Java applications. This MCP server enables an LLM to manage a Java application using JMX API via Jolokia.

https://github.com/user-attachments/assets/624ec93b-da69-49b5-be8f-02f2ff14bd2e

Distributions

Since version 0.4, the Jolokia MCP Server offers two distinct distributions to suit different deployment needs:

Standalone MCP Server

The Standalone MCP Server acts as a conventional MCP server; it is registered to the MCP host with either stdio or HTTP, and the MCP server itself communicates with your Java application, which must have a Jolokia agent attached, via JMX over HTTP.

To use the Standalone MCP Server, you'll first need to attach a Jolokia agent to your Java application. For detailed instructions on how to do this, please refer to the Jolokia manual:
https://jolokia.org/reference/html/manual/agents.html

JVM Agent MCP Server

In contrast, the JVM Agent MCP Server provides a streamlined, "drop-in" replacement for the standard Jolokia JVM Agent.

With this distribution, you simply attach the MCP Server's JVM Agent to your application instead of the standard Jolokia JVM Agent. The JVM Agent MCP Server then directly opens an HTTP port for the MCP protocol, effectively transforming your Java application itself into an MCP Server.

Features

This MCP server connects to a single JVM at startup and provides the following features on the connected JVM:

  • List MBeans from the connected JVM
  • List operations for a MBean
  • List attributes for a MBean
  • Read/write attributes of a MBean
  • Execute operations on a MBean

Tools

This MCP server provides 6 tools.

  • listMBeans
    • List available MBeans from the JVM
    • Output (List<String>): List of all MBean object names in the JVM
  • listMBeanOperations
    • List available operations for a given MBean
    • Inputs:
      • mbean (String): MBean name
    • Output (String): JSON-formatted definitions of all available operations for the given MBean
  • listMBeanAttributes
    • List available attributes for a given MBean
    • Inputs:
      • mbean (String): MBean name
    • Output (String): JSON-formatted definitions of all available attributes for the given MBean
  • readMBeanAttribute
    • Read an attribute from a given MBean
    • Inputs:
      • mbean (String): MBean name
      • attribute (String): Attribute name
    • Output (String): String representation of the given attribute's value or "null"
  • writeMBeanAttribute
    • Set the value to an attribute of a given MBean
    • Inputs:
      • mbean (String): MBean name
      • attribute (String): Attribute name
      • value (Object): Attribute value
    • Output (String): String representation of the given attribute's previous value or "null"
  • executeMBeanOperation
    • Execute an operation on a given MBean
    • Inputs:
      • mbean (String): MBean name
      • operation (String): Operation name
      • args (Object[]): Arguments
    • Output (String): String representation of the return value of the operation or "null"

Install

Standalone

Download the MCP server runner jar:

To install the Jolokia MCP server to a MCP host, add the following entry to the MCP settings:

{
  "mcpServers": {
    "jolokia": {
      "command": "java",
      "args": [
        "-jar",
        "<path-to-the-runner-jar>/jolokia-mcp-0.5.0-runner.jar"
      ]
    }
  }
}

Or if you prefer using JBang (no need for downloading the jar with this method):

{
  "mcpServers": {
    "jolokia": {
      "command": "jbang",
      "args": [
        "org.jolokia.mcp:jolokia-mcp-server:0.5.0:runner"
      ]
    }
  }
}

JVM Agent

Download the MCP server javaagent jar:

Then run your Java application with -javaagent option:

java -javaagent:jolokia-mcp-agent-jvm-0.5.0-javaagent.jar -jar your-app.jar

This would open the MCP HTTP transport at http://localhost:8779/mcp.

To register the Jolokia MCP server to a MCP host, add the following entry to the MCP settings:

{
  "mcpServers": {
    "jolokia": {
      "httpUrl": "http://localhost:8779/mcp"
    }
  }
}

Run

Run it with java -jar:

java -jar jolokia-mcp-server-0.5.0-runner.jar [Jolokia URL]

Using JBang, you can directly run it with the Maven GAV (org.jolokia.mcp:jolokia-mcp-server:0.5.0:runner):

jbang org.jolokia.mcp:jolokia-mcp-server:0.5.0:runner

HTTP Transport

By default, this MCP server runs with stdio transport. To switch it to HTTP transport, use the --sse option:

java -jar jolokia-mcp-server-0.5.0-runner.jar --sse

The HTTP transport endpoint by default launches at http://localhost:8080/mcp.

Config Options

Parameter/Option Default Description
Positional parameter http://localhost:8778/jolokia The Jolokia endpoint URL the MCP server connects to
--sse false (stdio) Enable HTTP transport
-D*=* System properties

The system properties that are relevant to the MCP server:

System property Default Description
quarkus.http.port 8080 (SSE) The port for the SSE endpoint
quarkus.mcp.server.sse.root-path mcp (SSE) The root path for the SSE endpoint (http://localhost:8080/mcp/sse)
jolokia.mcp.url http://localhost:8778/jolokia Equivalent to the positional parameter
jolokia.mcp.preferred-http-method Not set Preferred HTTP method for Jolokia requests (GET or POST)

Build

mvn clean install

Yorumlar (0)

Sonuc bulunamadi