A Model Context Protocol (MCP) server for Uptime Kuma version 2.
A Model Context Protocol (MCP) server for Uptime Kuma version 2. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.
A docker-compose.yml file is provided in the repository. Download it, configure your environment variables, and run:
Everything the assistant can do here goes through one of these:
Monitors — The Monitors tool exposed by this serverHeartbeats — The Heartbeats tool exposed by this serverNotifications — The Notifications tool exposed by this serverTags — The Tags tool exposed by this serverMaintenance — The Maintenance tool exposed by this serverFiltering — getMonitorSummary and listMonitors support filtering by:Installation goes through your MCP client rather than a global install: point it at args on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 5 environment variables: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Monitors, Heartbeats, Notifications and 3 more — is a fair guide to whether it matches your workflow. It is maintained by DavidFuchs; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Monitors | The Monitors tool exposed by this server. |
| Heartbeats | The Heartbeats tool exposed by this server. |
| Notifications | The Notifications tool exposed by this server. |
| Tags | The Tags tool exposed by this server. |
| Maintenance | The Maintenance tool exposed by this server. |
| Filtering | getMonitorSummary and listMonitors support filtering by: |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UPTIME_KUMA_URL | Endpoint or connection string the server talks to. | Yes |
| UPTIME_KUMA_USERNAME | Configuration value read at startup. | Optional |
| UPTIME_KUMA_PASSWORD | Configuration value read at startup. | Optional |
| UPTIME_KUMA_2FA_TOKEN | Credential the server authenticates with. | Yes |
| UPTIME_KUMA_JWT_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.