MCP server for Spring Boot Actuator analysis — health, metrics, environment, and bean diagnostics
Most database access work still happens through a UI a human drives. MCP Spring Boot Actuator MCP server moves it into the conversation instead. MCP server for Spring Boot Actuator analysis — health, metrics, environment, and bean diagnostics.
An MCP server that analyzes Spring Boot Actuator endpoints — health, metrics, environment, beans, startup, and caches. Detects issues, security risks, and provides actionable recommendations.
The server publishes 7 tools. What each one is for:
analyze_health — Parse and diagnose the /health endpoint response. Detects unhealthy components (database, Redis, Kafka, Elasticsearch, disk space) withanalyze_metrics — Analyze JVM, HTTP, and database pool metrics from /metrics endpointsanalyze_env — Analyze the /env endpoint for security risks and misconfigurationsanalyze_beans — The analyze_beans tool exposed by this serveranalyze_startup — Analyze the /startup actuator endpoint (Spring Boot 3.2+). Parses the startup timeline to detect slow bean initialization and heavyanalyze_caches — Analyze the /caches actuator endpoint. Lists registered caches and detects configuration issuesanalyze_loggers — Analyze the /loggers actuator endpoint. Detects verbose logging configurations that impact performance and security in productionThe server ships on npm as mcp-spring-boot-actuator, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Spring Boot Actuator's toolset — analyze_health, analyze_metrics, analyze_env and 4 more — is a fair guide to whether it matches your workflow. It is maintained by dmitriusan; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| analyze_health | Parse and diagnose the /health endpoint response. Detects unhealthy components (database, Redis, Kafka, Elasticsearch, disk space) with component-specific recommendations. |
| analyze_metrics | Analyze JVM, HTTP, and database pool metrics from /metrics endpoints. |
| analyze_env | Analyze the /env endpoint for security risks and misconfigurations. |
| analyze_beans | The analyze_beans tool exposed by this server. |
| analyze_startup | Analyze the /startup actuator endpoint (Spring Boot 3.2+). Parses the startup timeline to detect slow bean initialization and heavy auto-configurations. |
| analyze_caches | Analyze the /caches actuator endpoint. Lists registered caches and detects configuration issues. |
| analyze_loggers | Analyze the /loggers actuator endpoint. Detects verbose logging configurations that impact performance and security in production. |
{
"mcpServers": {
"spring-boot-actuator": {
"command": "npx",
"args": ["-y", "mcp-spring-boot-actuator"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.