Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"spring-monitoring": {
"command": "/absolute/path/to/spring-monitoring-mcp-server/run-mcp-server.sh"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Let AI agents monitor your Spring Boot services using the Model Context Protocol (MCP).
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / developer-tools
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for Spring Monitoring Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Let AI agents monitor your Spring Boot services using the Model Context Protocol (MCP).
This is a production-ready MCP server that allows AI agents (Claude Code, etc.) to:
HttpClient with configurable timeoutsmvnw wrapper)cd /absolute/path/to/spring-monitoring-mcp-server
./mvnw clean compile
Add this MCP server to your Claude Code settings file (~/.claude/settings.json):
{
"mcpServers": {
"spring-monitoring": {
"command": "/absolute/path/to/spring-monitoring-mcp-server/run-mcp-server.sh"
}
}
}
Or create a local .mcp.json file in your project:
{
"mcpServers": {
"spring-monitoring": {
"command": "/absolute/path/to/spring-monitoring-mcp-server/run-mcp-server.sh"
}
}
}
http://localhost:3450/tools/checkServiceHealth
{
"serviceUrl": "http://localhost:{your-running-application-port}"
}
or test the metrics endpoint:
http://localhost:3450/tools/getServiceMetrics
{
"serviceUrl": "http://localhost:{your-running-application-port}"
}
Start Claude Code and ask:
Check the health of my service at http://localhost:{your-running-application-port}
or
Get metrics from http://localhost:{your-running-application-port}
checkServiceHealthCheck if a Spring Boot service is up and measure its response time.
Input:
{
"serviceUrl": "http://localhost:{your-running-application-port}"
}
Output:
{
"serviceUrl": "http://localhost:{your-running-application-port}",
"status": "UP",
"statusCode": 200,
"responseTimeMs": 45,
"body": {
"status": "UP",
"components": {...}
}
}
getServiceMetricsFetch Spring Boot Actuator metrics from a service.
Input:
{
"serviceUrl": "http://localhost:{your-running-application-port}"
}
Output:
{
"serviceUrl": "http://localhost:{your-running-application-port}",
"status": "UP",
"statusCode": 200,
"responseTimeMs": 32,
"metrics": {
"names": ["jvm.memory.used", "http.server.requests", ...]
}
}
This MCP server uses a stdio transport model:
Claude Code <--JSON-RPC 2.0--> MCP Server <--HTTP--> Your Spring Boot Services
(stdio) (REST)
/actuator/health/actuator/metricsclaude mcp list
You should see spring-monitoring in the list.
... [View full README on GitHub](https://github.com/heyEdem/spring-monitoring-mcp-server#readme)