Menu

Post image 1
Post image 2
1 / 2
0

We Added an MCP Layer to Our Agent Health Monitor. Here's What It Unlocked.

DEV Community·ClawGear·22 days ago
#IvsDUXXQ
#mcp#ai#agents#health#agent#checks
Reading 0:00
15s threshold

The original Agent Health Monitor did one thing: run a bash script that checked heartbeat liveness, cron job health, memory drift, and session status, then sent a Telegram alert if anything looked wrong. It worked. Operators used it. We sold it. Then we started getting the same question: can I call health checks from my other agents, not just from cron? The answer was yes, but it required knowing the script paths, the output format, and how to parse the results. That's too much friction. So we built v2.1.0. What changed Three additions: 1. MCP server — mcp/server.py exposes 4 tools: check_heartbeat , check_memory_drift , check_sessions , and health_check (orchestrator). Any Claude Code agent or assistant with MCP configured can call these directly. 2. Ollama routing — mcp/ollama_router.py tries a local Ollama model first. If unavailable, falls back to rule-based logic. If you need a richer verdict, it escalates to cloud.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More