mcp-uptime-kuma
Seven fixes merged into the Uptime Kuma MCP server, so an AI assistant's monitor changes actually stick.
- Status
- Merged upstream
- Timeline
- Aug 2026 to 15 Aug 2026
- Built with
- TypeScript, Model Context Protocol, Uptime Kuma
- Links
- Source on GitHub
The Uptime Kuma MCP server lets an AI assistant read and manage monitors. Using it to run my own homelab’s monitoring, I kept finding places where it reported success and had quietly done something else. Seven fixes were merged upstream:
- monitor write fields that were silently dropped now save, and each write is checked to have actually persisted rather than trusting “Saved.”
- unknown arguments are rejected instead of silently stripped
- credentials are withheld from the read tools by default
- a lost Uptime Kuma session recovers instead of wedging the server
- heartbeat ordering, a staleness signal and limit aliases
- the integration tests can no longer be redirected by stray environment variables