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.

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

• Standalone MCP Server
• JVM Agent 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

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.

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

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"

Download the MCP server runner jar:

• jolokia-mcp-server-0.4.3-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.4.3-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.4.3:runner"
      ]
    }
  }
}

Download the MCP server javaagent jar:

• jolokia-mcp-agent-jvm-0.4.3-javaagent.jar

Then run your Java application with -javaagent option:

java -javaagent:jolokia-mcp-agent-jvm-0.4.3-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 it with java -jar:

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

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

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

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.4.3-runner.jar --sse

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

The system properties that are relevant to the MCP server:

mvn clean install