Menu
List monitors, fetch details, and pause or resume monitors in UptimeRobot.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Modify an existing UptimeRobot monitor — rename, change URL/interval, swap alert contacts, retag, tweak HTTP/keyword/API/heartbeat settings, and toggle SSL or domain reminders.
Choose between monitor groups and tags for organizing monitors — group membership is opaque and write-only over MCP, so tags are usually the better default.
Create and publish a public status page from monitors, groups, or tags, and manage announcements (incident, maintenance, info notices) on it.
Pause (or resume) many UptimeRobot monitors at once — by tag, search term, or state — around a deployment or maintenance window.
End-to-end incident workflow — find what's down, diagnose it, pause flapping monitors, and verify recovery.
Schedule one-off or recurring maintenance windows that suppress alerts for planned downtime, as an alternative to bulk-pause.
| name | manage-monitors |
| description | List monitors, fetch details, and pause or resume monitors in UptimeRobot. |
| tags | ["monitoring","list","pause","resume","uptimerobot"] |
Preflight — read first. If you cannot see any
uptimerobot:*MCP tools in your tool list, invoke theuptimerobot:setupskill before doing anything else. Do not tell the user the MCP is misconfigured —setup's Step 0 detects the common case (server connected, tools loaded after session start) and resolves it without re-keying.
Covers monitor discovery and status control:
list-monitors — paginated discovery with search + state filters.get-monitor-details — full config for one monitor.update-monitor-status — pause or resume.For creating monitors see the create-*-monitor skills. For editing an existing monitor's configuration (rename, URL, interval, alert contacts, tags, type-specific settings) see update-monitor.
{
"search": "api",
"filter": ["DOWN"],
"limit": 50
}
Parameters:
search — full-text match against friendlyName and url.filter — array, any of UP, DOWN, PAUSED, NOT_STARTED, EXPIRING_DOMAIN, EXPIRING_SSL_CERTIFICATE, WITH_API_KEY, WITHOUT_API_KEY.limit — page size (clamped server-side).cursor — from the previous page's nextCursor.The response includes an instructions field with the exact next-page call JSON. Follow it verbatim.
{ "monitorId": 800123456 }
Returns the full config (type, URL, interval, thresholds, alert contacts, tags, type-specific fields) plus current status and state duration. Use this:
create-monitor / update-monitor took effect.Covered in its own skill: update-monitor — rename, URL, interval, alert contacts, tags, HTTP/keyword/API/heartbeat type-specific settings, and read‑modify‑write patterns for array fields.
{ "monitorId": 800123456, "status": "PAUSED" }
status is one of PAUSED (stop monitoring) or STARTED (resume). Resuming a paused monitor can return -28001 monitor_limit_exceeded if the account is over its active-monitor cap.
get-monitor-details after a status change. Replication lag can mean the next list-monitors call still shows the old state.update-monitor-status when the authorized account lacks write access — returns -31002 access_denied.-28001 monitor_limit_exceeded.update-monitor — edit configuration of an existing monitor.bulk-pause — pause/resume many monitors at once.incidents — downtime history for a monitor.stats — aggregated uptime / response-time metrics.errors — recovering from -28001, -28002, -29001, -31002.