Jolokia MCP Server
@jolokia
Let LLMs manage your Java application via JMX/Jolokia 🌶️
Overview
What is Jolokia MCP Server?
Jolokia MCP Server is an MCP server for Jolokia, a JMX-HTTP bridge for Java applications. It enables an LLM to manage a Java application using the JMX API via Jolokia. The server connects to a single JVM at startup and is available as a standalone MCP server or a JVM Agent MCP Server.
How to use Jolokia MCP Server?
You can run the standalone server with java -jar jolokia-mcp-server-0.5.1-runner.jar [Jolokia URL] or via JBang. For the JVM Agent distribution, attach it to your application with -javaagent:jolokia-mcp-agent-jvm-0.5.1-javaagent.jar. Register the server in your MCP host settings using either stdio or HTTP transport.
Key features of Jolokia MCP Server
- List MBeans from the connected JVM
- List operations for a given MBean
- List attributes for a given MBean
- Read and write attributes of an MBean
- Execute operations on an MBean
- Supports both stdio and HTTP (SSE) transport
Use cases of Jolokia MCP Server
- An LLM managing Java application JMX MBeans in real time
- Automating monitoring and configuration of a running JVM
- Integrating JMX-based management into AI-driven workflows
- Replacing the standard Jolokia JVM Agent to embed MCP directly
FAQ from Jolokia MCP Server
What distributions are available?
Two distributions: Standalone MCP Server (communicates with your Java app via JMX over HTTP) and JVM Agent MCP Server (a drop-in replacement for the standard Jolokia JVM Agent that transforms your app into an MCP server).
What tools does this MCP server provide?
It provides six tools: listMBeans, listMBeanOperations, listMBeanAttributes, readMBeanAttribute, writeMBeanAttribute, and executeMBeanOperation.
How do I configure the Jolokia URL?
Pass it as a positional argument when running the server (java -jar ... http://localhost:8778/jolokia) or set the system property jolokia.mcp.url. The default is http://localhost:8778/jolokia.
What transport options are available?
By default, the server uses stdio transport. You can switch to HTTP transport (SSE) by adding the --sse flag when starting the server.
Does it require Java to run?
Yes, the Jolokia MCP Server requires a Java runtime (JVM) to execute, as it is distributed as a JAR or JBang artifact.