uptime-kuma-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_monitorsA | Batch add multiple monitors to Uptime Kuma, returns Uptime Kuma page URL after completion |
| get_monitorsA | Get all monitors list, returns trimmed fields to prevent long context, returns Uptime Kuma page URL after completion |
| delete_monitorsA | Batch delete multiple monitors, returns Uptime Kuma page URL after completion |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: adding, deleting, or getting monitors. There is no overlap.
All tools follow a consistent verb_noun pattern (add_monitors, delete_monitors, get_monitors).
3 tools is slightly minimal but reasonably scoped for basic monitor management.
Missing an update operation for monitors, which is a notable gap in CRUD coverage.