create_maintenance_window

sh.fettle/mcp · Verify this server

Create a maintenance window that silences alerts for a time. Requires a key with the write scope. Required: name (1 to 255 characters), scope, dtstart and duration_minutes. enabled (boolean, default true): false stores it without effect. During a window the covered monitors keep being checked, but no incident opens and no alert goes out; use a window rather than pausing monitors around a deploy or reboot. scope is ORG (every monitor of the organization, monitor_ids ignored) or MONITOR (only monitor_ids, a list of monitor uuids from list_monitors, at least one; an id that is not a monitor of this organization is a 404). dtstart is the first start as an ISO 8601 date-time in local wall-clock time of timezone, for example 2026-10-14T22:00:00; a UTC offset or Z is a 422. duration_minutes (integer, 1 to 40320) is how long each occurrence lasts. rrule (at most 1024 characters) repeats it, as a single iCal RRULE without the RRULE: prefix, for example FREQ=WEEKLY;BYDAY=SU;BYHOUR=3; hourly, minutely and secondly frequencies are refused. timezone (IANA name such as Europe/Berlin, at most 64 characters) is the zone the schedule repeats in, so a weekly 03:00 stays 03:00 across daylight-saving changes. Call preview_maintenance_window first to check a recurring schedule. Omit rrule for a one-time window. When timezone is omitted the organization's timezone is used. The plan caps how many windows an organization may have (403 past it or when the plan has none; see max_maintenance_windows in get_plan_usage). Other errors: 422 for an invalid argument or schedule, naming it. Returns the window. Example: {"name": "Deploy", "scope": "MONITOR", "monitor_ids": ["<id from list_monitors>"], "dtstart": "2026-10-14T22:00:00", "duration_minutes": 30}