MCP Spring Boot Actuator
About
Spring Boot Actuator MCP server — analyzes health, metrics, environment, beans, and startup endpoints. Detects configuration issues and security risks with actionable recommendations.
Details
- Author
- dmitriusan
- Categories
- Developer Tools
Jump to
Setup
Install MCP Spring Boot Actuator in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/dmitriusan/mcp-spring-boot-actuator
Follow the installation instructions in the repository README, then restart your MCP client.
An MCP server that analyzes Spring Boot Actuator endpoints — health, metrics, environment, beans, startup, and caches. Detects issues, security risks, and provides actionable recommendations.
There isno other MCP serverthat analyzes Spring Boot Actuator endpoints. This is the only tool that lets your AI assistant understand your Spring Boot application's health, performance, configuration, and startup behavior through actuator data.
7 analytical tools turn raw actuator JSON into actionable diagnostics — health checks, JVM metrics analysis, security risk detection in environment/beans, startup bottleneck identification, and cache efficiency analysis.
Generate exportable diagnostic reports (HTML + PDF)with a Pro license key.
- Full JVM thread dump analysis report with actionable recommendations
- PDF export for sharing with your team
- Priority support
Pro license key activates thegenerate_reportMCP tool in mcp-jvm-diagnostics.
Parse and diagnose the/healthendpoint response. Detects unhealthy components (database, Redis, Kafka, Elasticsearch, disk space) with component-specific recommendations.
curl http://localhost:8080/actuator/health | jq '.' > health.json
- DOWN/OUT_OF_SERVICE components
- Low disk space warnings (< 15% free)
- Nested component health (e.g., primary/secondary databases)
- Restricted health endpoints (noshow-details)
Analyze JVM, HTTP, and database pool metrics from/metricsendpoints.
# Collect metrics into a single JSON object: { "jvm.memory.used": 800000000, "jvm.memory.max": 1000000000, "jvm.threads.live": 150, "jvm.gc.pause.count": 500, "jvm.gc.pause.total": 8.5, "http.server.requests.count": 10000, "http.server.requests.error.count": 50, "hikaricp.connections.active": 8, "hikaricp.connections.max": 10 }
- Heap utilization >= 90% (CRITICAL) or > 75% (WARNING)
- High thread count (> 500)
- Long GC pauses (avg > 200ms)
- HTTP error rate > 10% (CRITICAL) or > 1% (WARNING)
- Connection pool exhaustion >= 90% (CRITICAL)
- Pending connection requests
Supports both flat metric values and Spring Boot measurement format ({ measurements: [{ statistic: "VALUE", value: N }] }).
Analyze the/envendpoint for security risks and misconfigurations.
curl http://localhost:8080/actuator/env | jq '.' > env.json
- Exposed secrets (passwords, API keys, tokens not masked with)
- Risky production configs:ddl-auto: create-drop, H2 console enabled,show-sql: true
- DevTools enabled in production
- All actuator endpoints exposed (management.endpoints.web.exposure.include=)
- Missing Spring profiles (no active profiles set)
Analyze the/beansendpoint for architectural issues.
curl http://localhost:8080/actuator/beans | jq '.' > beans.json
- Circular dependencies (A → B → A)
- Singleton beans depending on prototype-scoped beans (scope mismatch)
- Beans with > 10 dependencies (God objects)
- Large bean counts (> 500)
- Multiple application contexts
Analyze the/startupactuator endpoint (Spring Boot 3.2+). Parses the startup timeline to detect slow bean initialization and heavy auto-configurations.
curl -X POST http://localhost:8080/actuator/startup | jq '.' > startup.json
- json— The/startupendpoint JSON response
- Slow startup (> 30s CRITICAL, > 15s WARNING)
- Heavy auto-configurations consuming > 30% of startup time
- Slow bean initialization (> 2s per bean)
- Top slowest steps ranked by duration
Analyze the/cachesactuator endpoint. Lists registered caches and detects configuration issues.
curl http://localhost:8080/actuator/caches | jq '.' > caches.json
- json— The/cachesendpoint JSON response
- UnboundedConcurrentMapCacheusage (no eviction, will grow indefinitely)
- Too many caches (> 20, memory overhead)
- Missing cache managers (no Spring Cache configured)
- Empty cache registrations
Analyze the/loggersactuator endpoint. Detects verbose logging configurations that impact performance and security in production.
curl http://localhost:8080/actuator/loggers | jq '.' > loggers.json
- json— The/loggersendpoint JSON response
- ROOT logger set to DEBUG/TRACE (floods logs, degrades performance)
- Explicitly configured DEBUG/TRACE loggers (likely leftover from debugging)
- Verbose framework logging (Spring, Hibernate, HikariCP, Micrometer, Apache)
- Inconsistent log levels across related packages
- More than 5 verbose loggers (signs of leftover debug configuration)
Add to your Claude Desktop config (~/.claude/claude_desktop_config.json):
{ "mcpServers": { "spring-boot-actuator": { "command": "npx", "args": ["-y", "mcp-spring-boot-actuator"] } } }
Once configured, try these prompts in Claude:
- "Check the health of my Spring Boot app: [paste /actuator/health JSON]"— Detects DOWN components, low disk space, and provides component-specific recommendations
- "Are there any security risks in my config? [paste /actuator/env JSON]"— Finds exposed secrets, risky settings likeddl-auto: create-drop, and over-exposed endpoints
- "How is my app performing? [paste JVM/HTTP metrics]"— Analyzes heap usage, GC pressure, HTTP error rates, and connection pool utilization
- "Why is my app starting so slowly?" (paste/actuator/startupJSON)
- "Are my caches configured properly?" (paste/actuator/cachesJSON)
- Node.js 18+
- Spring Boot application with Actuator endpoints enabled
- mcp-db-analyzer— PostgreSQL/MySQL/SQLite schema analysis
- mcp-jvm-diagnostics— Thread dump and GC log analysis
- mcp-redis-diagnostics— Redis memory, slowlog, and client diagnostics
- mcp-migration-advisor— Flyway/Liquibase migration risk analysis
- Actuator endpoints must be exposed: Spring Boot secures actuator endpoints by default. You must explicitly expose endpoints viamanagement.endpoints.web.exposure.include.
- Startup analysis: Requires Spring Boot 3.2+ withmanagement.endpoint.startup.enabled=true. Older versions don't provide startup timing data.
- Single instance: Analyzes one application instance at a time. For clustered applications, point to each instance separately.
- Metric accumulation: Some metrics (HTTP request counts, error rates) require traffic to accumulate data. A freshly started app may show zeros.
- Environment masking: Spring Boot masks sensitive properties by default. Theanalyze_envtool sees masked values (e.g.,*) and cannot detect actual credential exposure in masked properties.
- Custom health indicators: The tool recognizes standard health indicator patterns. Custom health indicators with non-standard status values may not trigger specific recommendations.
- Cache analysis: Supports ConcurrentMapCache, Caffeine, Redis, and EhCache. Other cache providers may show limited analysis.
- Non-JSON responses: Handles HTML error pages (401, 403, 500) gracefully with "Invalid JSON" warnings, but cannot extract useful data from them.
- Circular dependency depth: Detects cycles of any length, including multi-hop chains (A→B→C→A).
This MCP server is no longer maintained or distributed. The Corporation has pivoted to Apify marketplace actors. Seeirrationalwayson Apifyandirrcorp/bzp-poland-tendersfor current Corporation work.
The npm package has been unpublished. The repository is archived for historical reference only.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Create crafted UI components inspired by the best 21st.dev design engineers.
Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent
ALAPI MCP Tools,Call hundreds of API interfaces via MCP
AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform
MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.
APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.
One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.
Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
