Stop Guessing JVM Bugs: Connect Claude Code to Spring Boot via Local MCP Actuator Servers A developer built a local Model Context Protocol (MCP) server that wraps Spring Boot Actuator endpoints, enabling Claude Code to diagnose and fix JVM bugs in real-time. The tool provides read-only access to runtime metrics, thread dumps, and bean configurations, allowing an AI agent to query application state, apply patches, and verify fixes without manual debugging. The project, hosted at javalld.com, aims to streamline debugging for Spring Boot developers. In 2026, if you are still manually digging through heap dumps or copy-pasting stack traces into a browser chat window to debug a failing Spring Boot app, you are wasting valuable engineering hours. By connecting Claude Code directly to your running JVM via a local Model Context Protocol MCP server mapped to Actuator endpoints, you let your AI terminal agent diagnose, patch, and verify runtime state in real-time. /actuator/metrics or /actuator/threaddump into an LLM UI, stripping out vital execution context. localhost with read-only runtime access.Bridge your local CLI agent directly to the running application context using a custom local MCP server that wraps the Spring Boot Actuator REST API. get thread dump , get active beans , and query metrics to Claude Code. claude locally and register the local Actuator MCP server in your agent configuration. application.yml or Java source, trigger a hot-reload, and immediately re-query Actuator to verify the fix.I built javalld.com while prepping for senior roles — complete LLD problems with execution traces, not just theory. Configure your local Claude Code environment to register the Spring Boot Actuator MCP bridge: // ~/.config/claude-code/mcp-config.json { "mcpServers": { "springboot-actuator": { "command": "npx", "args": "-y", "@mcp/server-springboot-actuator" , "env": { "ACTUATOR BASE URL": "http://localhost:8080/actuator", "ACTUATOR TOKEN": "local-dev-secret-token" } } } } Now, you can simply run: claude "Why is my database connection pool starving? Check the current HikariCP metrics and fix the config." HikariPool metrics on demand.