mcp-uptime-kuma
Provides tools for monitoring and managing Uptime Kuma monitors, including fetching summaries, heartbeats, and uptime, as well as creating, pausing, and deleting monitors, managing notifications, tags, maintenance windows, and status pages.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-uptime-kumashow me a summary of all monitors"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-uptime-kuma
A Model Context Protocol (MCP) server for Uptime Kuma version 2. Supports stdio and streamable HTTP transports.
Features
Real-time Monitoring: Access monitors, heartbeats, uptime, and responsiveness metrics via Socket.IO with instant status change notifications.
Context-Friendly: Returns only essential data by default to avoid overwhelming LLM context windows.
Multiple Transports: Supports stdio (local) and streamable HTTP (remote) transports.
Quick Start
Using npx (stdio transport)
Add this to your MCP client configuration:
{
"mcpServers": {
"uptime-kuma": {
"command": "npx",
"args": ["-y", "@davidfuchs/mcp-uptime-kuma"],
"env": {
"UPTIME_KUMA_URL": "http://your-uptime-kuma-instance:3001",
"UPTIME_KUMA_USERNAME": "your_username",
"UPTIME_KUMA_PASSWORD": "your_password"
}
}
}
}Using Docker (streamable HTTP transport)
Option 1: Docker Run
docker run -d \
--name mcp-uptime-kuma \
-p 3000:3000 \
-e UPTIME_KUMA_URL=http://your-uptime-kuma-instance:3001 \
-e UPTIME_KUMA_USERNAME=your_username \
-e UPTIME_KUMA_PASSWORD=your_password \
davidfuchs/mcp-uptime-kuma:latest \
-t streamable-httpOption 2: Docker Compose
A docker-compose.yml file is provided in the repository. Download it, configure your environment variables, and run:
docker compose up -dThen configure your MCP client to connect to the endpoint:
{
"mcpServers": {
"uptime-kuma": {
"url": "http://localhost:3000/mcp"
}
}
}See Authentication Methods for JWT token and anonymous authentication options.
Example Conversation
Conversation in LibreChat where the mcp-uptime-kuma server is providing real-time information from Uptime Kuma.
Available Tools
Monitors
Tool | Purpose |
| Get a quick overview of all monitors with their current status. Supports filtering. |
| Get the full list of all monitors with configurations. Supports filtering. |
| Get all available monitor types supported by Uptime Kuma. |
| Get detailed configuration for a specific monitor by ID. |
| Create a new monitor (requires name and type at minimum). |
| Update an existing monitor's configuration. |
| Permanently delete a monitor and all its heartbeat history. |
| Pause a monitor to stop performing checks. |
| Resume a paused monitor to restart checks. |
Heartbeats
Tool | Purpose |
| Get status check history for all monitors. |
| Get status check history for a specific monitor. |
Notifications
Tool | Purpose |
| List all configured notification channels (Slack, Discord, email, webhooks, etc.). |
| Create a new notification channel. |
| Update an existing notification channel. |
| Permanently delete a notification channel. |
Tags
Tool | Purpose |
| List all tags defined in Uptime Kuma. |
| Create a new tag that can be assigned to monitors. |
| Permanently delete a tag (removes it from all monitors). |
Maintenance
Tool | Purpose |
| List all scheduled maintenance windows. |
| Schedule a new maintenance window. |
Status Pages & Settings
Tool | Purpose |
| List all configured status pages. |
| Get Uptime Kuma server settings. |
Filtering
getMonitorSummary and listMonitors support filtering by:
keywords: Space-separated keywords for fuzzy matching against monitor pathNames
type: Monitor type(s), comma-separated (e.g.,
"http","http,ping,dns")active: Filter by active (
true) or inactive (false) monitorsmaintenance: Filter by maintenance mode status
tags: Tag name and optional value, comma-separated (e.g.,
"production","env=staging")status (getMonitorSummary only): Heartbeat status (
"0"=DOWN,"1"=UP,"2"=PENDING,"3"=MAINTENANCE)
Examples:
getMonitorSummary({ status: "0" }) // All DOWN monitors
getMonitorSummary({ type: "http", maintenance: true }) // HTTP monitors in maintenance
listMonitors({ tags: "production,region=us-east" }) // Monitors with specific tagsAuthentication Methods
Anonymous Authentication
If authentication is disabled on your Uptime Kuma instance, only UPTIME_KUMA_URL is required.
Username/Password Authentication
UPTIME_KUMA_URL=http://your-instance:3001
UPTIME_KUMA_USERNAME=your_username
UPTIME_KUMA_PASSWORD=your_password
UPTIME_KUMA_2FA_TOKEN=123456 # Optional, only if 2FA is enabledJWT Token Authentication
Recommended for 2FA users. Takes precedence over username/password if both are provided.
UPTIME_KUMA_URL=http://your-instance:3001
UPTIME_KUMA_JWT_TOKEN=your_jwt_tokenObtaining Your JWT Token
Using the CLI utility (recommended):
npx -p @davidfuchs/mcp-uptime-kuma mcp-uptime-kuma-get-jwt http://localhost:3001 admin mypasswordUsing Docker:
docker run --rm davidfuchs/mcp-uptime-kuma:latest get-jwt http://host.docker.internal:3001 admin mypasswordFrom browser: Open Developer Tools → Storage/Application → Local Storage → find token key.
LibreChat Configuration
stdio transport:
mcpServers:
uptime-kuma:
command: npx
args: ["-y", "@davidfuchs/mcp-uptime-kuma"]
env:
UPTIME_KUMA_URL: "http://your-instance:3001"
UPTIME_KUMA_USERNAME: "your_username"
UPTIME_KUMA_PASSWORD: "your_password"
serverInstructions: truestreamable HTTP transport:
Update the allowed domains to whatever domain you're using in the URL (e.g., localhost or host.docker.internal for Docker setups):
mcpServers:
uptime-kuma:
type: streamable-http
url: "http://mcp-uptime-kuma:3000/mcp"
serverInstructions: true
mcpSettings:
allowedDomains:
- 'mcp-uptime-kuma'Contributing
For development setup, building, testing, and project structure, see CONTRIBUTING.md.
Learn More
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DavidFuchs/mcp-uptime-kuma'
If you have feedback or need assistance with the MCP directory API, please join our Discord server