The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Jvm MCP Server listing page.
A lightweight JVM monitoring and diagnostic MCP (Multi-Agent Communication Protocol) server implementation based on native JDK tools. Provides AI agents with powerful capabilities to monitor and analyze Java applications without requiring third-party tools like Arthas.
A hosted deployment is available on Fronteir AI.
JVM-MCP-Server provides a comprehensive set of tools for JVM monitoring and diagnostics:
list_java_processes: List all Java processesget_thread_info: Get thread information for a specific processget_jvm_info: Get JVM basic informationget_memory_info: Get memory usage informationget_stack_trace: Get thread stack trace informationget_class_info: Get detailed class information including structureget_stack_trace_by_method: Get method call pathdecompile_class: Decompile class source codesearch_method: Search for methods in classeswatch_method: Monitor method invocationsget_logger_info: Get logger informationset_logger_level: Set logger levelsget_dashboard: Get system resource dashboardget_jcmd_output: Execute JDK jcmd commandsget_jstat_output: Execute JDK jstat commandsFor detailed documentation on each tool, see Available Tools.
JVM-MCP-Server is built on a modular architecture:
BaseCommand: Abstract base class for all commandsCommandExecutor: Interface for command execution (local and remote)OutputFormatter: Interface for formatting command outputJvmMcpServer: Main server class that registers all toolsThe project is in active development. See Native_TODO.md for current progress.
Contributions are welcome! Please feel free to submit a Pull Request.
git checkout -b feature/amazing-feature)git commit -m 'Add some amazing feature')git push origin feature/amazing-feature)This project is licensed under the MIT License - see the LICENSE file for details.
NP|## Acknowledgements
#MH|
#TK|- JDK tools documentation
#WY|- FastMCP protocol specification
#JK|- Contributors and testers
#BP|
#KG|## Permission Requirements
#YM|
#KB|Some JVM diagnostic commands (jstack, jmap, jinfo, jcmd, etc.) require sufficient permissions to attach to the target JVM process. If you encounter permission errors, try the following solutions:
#YB|
#KB|### Common Errors
#RR|
#KB|- Permission denied: Insufficient permissions
#YZ|- Unable to open socket file: Cannot connect to JVM process
#KD|- No such process: Process does not exist or has exited
#MH|
#KB|### Solutions
#BR|
#KB|1. Run with sudo (recommended): sudo uv run jvm-mcp-server
#XZ|2. Run as the same user as target Java process: Check the user ID of the Java process and run as that user
#HM|3. Add experimental attach permission to JDK: Add to JVM startup arguments:
#XQ|4. In Docker: Ensure the container has sufficient permissions (--privileged or mount /proc)
#KB|
#KB|Note: list_java_processes uses the jps command and does not require special permissions. Other commands may need to be configured according to the solutions above.