Allows managing Uptime Kuma monitors and groups via CSV-based sync operations, including creating, updating, and previewing changes to monitor configurations.
Click on "Deploy 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., "@kuma-mcp preview sync from CSV"
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.
Proof of concept for a minimal Kuma MCP-compatible wrapper using the existing CSV-driven Kuma API builder.
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
main.py
main_mcp.py
monitor.csv
requirements.txt
.env.example
kuma_builder/config.py
kuma_builder/inventory.py
kuma_builder/kuma_client.py
kuma_builder/sync.py
kuma_builder/mcp_protocol.py
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_MEpython 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.
--prune is a placeholder and currently does not delete anything.
main_mcp.py is a PoC wrapper with a minimal JSON-style command interface.
JSON output can be consumed by automation or a higher-level MCP wrapper.
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.
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.
This server cannot be deployed
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.
Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.
