Uptime Kuma FAQs

Question 1

How does mcp-uptime-kuma benefit LLMs?

Accepted Answer

It's optimized for LLM context windows, delivering only essential monitoring data by default to prevent overwhelming the model. This allows LLMs to efficiently query monitor statuses, configurations, and manage Uptime Kuma instances with minimal token usage.

Question 2

What authentication methods are available for connecting to Uptime Kuma?

Accepted Answer

mcp-uptime-kuma supports anonymous access (if disabled on your Uptime Kuma instance), username/password authentication, and JWT token authentication. Using a JWT token is recommended, especially for Uptime Kuma instances with 2FA enabled.

Question 3

What is mcp-uptime-kuma?

Accepted Answer

mcp-uptime-kuma is a Model Context Protocol (MCP) server that seamlessly connects Large Language Models (LLMs) to your Uptime Kuma monitoring instances. It provides real-time access to monitoring data and enables direct control over your monitors via an LLM interface.

Question 4

Which transport methods does mcp-uptime-kuma support?

Accepted Answer

It supports both `stdio` for local execution (e.g., via npx) and `streamable HTTP` for remote access (e.g., deployed via Docker), offering flexibility in how you integrate it with your MCP client.

Question 5

What Uptime Kuma actions can I perform using this tool?

Accepted Answer

You gain a full suite of management capabilities including listing monitors, getting detailed configurations, pausing/resuming monitors, querying heartbeat histories, and retrieving Uptime Kuma server settings. Comprehensive filtering options are also available for monitor lists.

Uptime Kuma

Uptime Kuma

Key Features

Use Cases

Key Features

Use Cases