maintenance-windows

Maintenance windows

Preflight — read first. If you cannot see any uptimerobot:* MCP tools in your tool list, invoke the uptimerobot:setup skill 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.

Requires the maintenance-window plan feature.

Decision: maintenance window vs. bulk-pause

Both stop alert noise during planned downtime, but they work differently:

	Maintenance window	bulk-pause
What changes	Alerts only — monitor keeps checking and its state stays visible	Monitor itself stops checking (status: PAUSED)
Timing	Scheduled in advance, can recur	Immediate, manual resume
Resume cap risk	None — monitor was never paused	Resuming can hit -28001 monitor_limit_exceeded
Best for	Known, recurring, or future-dated downtime (deploy windows, patching schedule)	Ad-hoc, right-now, or a monitor that needs to fully stop

Default to a maintenance window whenever the downtime is planned ahead of time or repeats. Use bulk-pause for "pause it right now" requests.

Creating a window

{
  "name": "Weekly DB patching",
  "interval": "weekly",
  "date": "2026-07-06",
  "time": "02:00:00",
  "duration": 90,
  "days": [1],
  "monitorIds": [800111, 800222]
}

• date/time are the first occurrence; time is UTC — confirm the user's intended timezone and convert before calling.
• days is required for weekly (1–7, ISO weekday) and monthly (1–31, or -1 for "last day of the month") recurrence. Omitting it on a recurring window is a validation error, not a silent default.
• duration is minutes the window stays active from the daily start time — not an end date.
• autoAddMonitors: true includes every monitor, including ones created later. Confirm with the user before using it — it's easy to end up suppressing alerts for something unrelated.