analyze_beans
Analyze Spring Boot Actuator /beans endpoint response. Detects circular dependencies, scope mismatches, and bean architecture issues.
LABSCO SUMMARY
Nothing here connects to your application — you bring the JSON, which is exactly what makes it usable against an environment you cannot reach.
Each tool maps to one Actuator endpoint and takes that endpoint's response as its argument, so the server never needs network access to the service under diagnosis and never needs its credentials. That fits the common case where the Actuator endpoints sit behind a VPN or an operations proxy: you can copy a response out but you cannot expose the port. analyze_env is often the one worth running first, because its findings are about exposure rather than performance — exposed secrets and risky configuration — and it is the one that costs something to leave unrun.
What it is
A Spring Boot Actuator response analyser with seven tools, one per endpoint, each taking that endpoint's JSON as its input.
What you get
- Health: analyze_health diagnoses the unhealthy components in a /health response and returns recommendations.
- Metrics: analyze_metrics detects JVM heap pressure, non-heap metaspace pressure, high error rates, connection pool exhaustion and GC issues.
- Configuration exposure: analyze_env reads an /env response for exposed secrets, risky configurations and missing production settings.
- Application structure: analyze_beans detects circular dependencies, scope mismatches and bean architecture issues, and analyze_startup reads the /startup endpoint available from Spring Boot 3.2 onward for slow bean initialisation, heavy auto-configurations and startup bottlenecks.
- Caches and logging: analyze_caches lists the registered caches and flags unbounded ones as a memory-leak risk, and analyze_loggers detects DEBUG or TRACE levels in production, inconsistent levels across packages and verbose framework logging.
Requirements
The Actuator endpoint responses themselves as JSON — every tool takes the JSON rather than a URL, so reaching the endpoints is your job. analyze_startup needs the /startup endpoint, which its description places at Spring Boot 3.2 and later. No credentials are configured.
Setup effort
One command — npx -y mcp-spring-boot-actuator
USE CASES
01
Diagnosing a service that reports itself unhealthy
Analyse the health response for which components are failing, then read the metrics for the pressure behind it.
02
Finding memory pressure before it becomes an outage
Read heap and metaspace pressure out of the metrics, then check whether an unbounded cache is what is filling it.
03
Checking a configuration for things it should not be publishing
Scan the environment response for exposed secrets and risky settings, and check the log levels for debug output left on in production.
04
Working out why the application takes so long to start
Read the startup timings for slow beans and heavy auto-configuration, then look at the bean graph for the structural reason.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
analyze_caches
Analyze Spring Boot Actuator /caches endpoint. Lists registered caches, detects unbounded caches (memory leak risk), and identifies cache configuration issues.
analyze_env
Analyze Spring Boot Actuator /env endpoint response. Detects exposed secrets, risky configurations, and missing production settings.
analyze_health
Analyze a Spring Boot Actuator /health endpoint response. Diagnoses unhealthy components and provides recommendations.
analyze_loggers
Analyze Spring Boot /loggers endpoint response. Detects DEBUG/TRACE in production, inconsistent log levels across packages, and verbose framework logging.
analyze_metrics
Analyze Spring Boot Actuator metrics data. Detects JVM heap pressure, non-heap (metaspace) pressure, high error rates, connection pool exhaustion, and GC issues.
analyze_startup
Analyze Spring Boot Actuator /startup endpoint (Spring Boot 3.2+). Detects slow bean initialization, heavy auto-configurations, and startup bottlenecks.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected. Every tool analyses actuator JSON you fetch yourself; the server never connects to your application. analyze_env sees only values Spring Boot has already masked.
Requires
- npx on PATH
- Node.js 18+
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-spring-boot-actuatorMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"spring-boot-actuator": {
"command": "npx",
"args": [
"-y",
"mcp-spring-boot-actuator"
]
}
}
}
