kuma-mcp
Allows managing Uptime Kuma monitors and groups via CSV-based sync operations, including creating, updating, and previewing changes to monitor configurations.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Uptime Kuma MCP PoC
Proof of concept for a minimal Kuma MCP-compatible wrapper using the existing CSV-driven Kuma API builder.
Why
This project demonstrates a protocol-friendly interface on top of the Uptime Kuma API sync engine. It reuses the existing builder backend while exposing a PoC MCP-style command entrypoint.
Related MCP server: mcp-uptime-kuma
Project Layout
main.pymain_mcp.pymonitor.csvrequirements.txt.env.examplekuma_builder/config.pykuma_builder/inventory.pykuma_builder/kuma_client.pykuma_builder/sync.pykuma_builder/mcp_protocol.py
Setup
cd /home/sladmin/kuma_mcp
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
cp .env.example .envEdit .env:
KUMA_URL=http://127.0.0.1:3001
KUMA_USER=admin
KUMA_PASSWORD=CHANGE_MEUsage
python main.py --csv monitor.csv
python main.py --csv monitor.csv --dry-run
python main.py --csv monitor.csv --prune
python main_mcp.py --csv monitor.csv --action syncInventory --output json
python main_mcp.py --csv monitor.csv --action previewSync --output json
python main_mcp.py --csv monitor.csv --action status --output jsonNotes:
Default behavior is non-destructive: create missing and update existing.
--pruneis a placeholder and currently does not delete anything.main_mcp.pyis a PoC wrapper with a minimal JSON-style command interface.JSON output can be consumed by automation or a higher-level MCP wrapper.
Idempotency Rules
Matches are based on normalized full path + name.
Group rows create/reuse recursive parent groups.
Existing monitors at the same full path are updated when configuration changes.
Re-running should not create duplicates when entries are unchanged.
Acceptance Check
Run the script against
monitor.csv.Open Uptime Kuma and verify groups are nested under
SoftLab Monitoring Root.Re-run the script and verify there are no duplicates.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Manage uptime monitors, incidents and status pages from any MCP client.
MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents.
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. This MCP server lets your agent create, update, pause and delete checks, build dashboards and publish them as status pages, manage notification groups, and read incidents with their causes, uptime, run history and latency. Pause, delete and unpublish stay off until you turn them on. Browser sign-in, no API key needed.
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables unified management of maintenance windows and incidents across Atlassian Statuspage and Uptime Kuma. It allows AI assistants to schedule maintenance, update service statuses, and list monitors through a single MCP-compatible interface.9MIT
- AlicenseAqualityAmaintenanceMCP server for Uptime Kuma that enables monitoring and management of uptime monitors, heartbeats, notifications, tags, and maintenance windows via natural language.36702 npm70MIT
- AlicenseAqualityDmaintenanceEnables managing Uptime Kuma monitors via MCP protocol, supporting batch add, list, and delete operations.39MIT
- AlicenseAqualityBmaintenanceEnables managing Uptime Kuma monitoring through natural language, including creating, editing, pausing, and deleting monitors, plus retrieving heartbeats, status, metrics, notifications, and status pages.12MIT