Uptime Kuma MCP Server

Example Use Cases

• 1

  Programmatically add, edit, pause, or delete monitors in Uptime Kuma.

• 2

  Retrieve monitor heartbeats and status page details asynchronously.

• 3

  Manage monitor tags and fetch paginated heartbeat data from Uptime Kuma.

Description

This MCP server acts as an intermediary to interact with an Uptime Kuma instance, exposing asynchronous tools to manage monitors, tags, status pages, and retrieve heartbeat data. It integrates with the Uptime Kuma API using a synchronous client wrapped for async use, enabling efficient non-blocking operations. Configuration is managed via environment variables, and the server supports both STDIO and SSE communication modes.