Skip to main content
Glama
DavidFuchs

mcp-uptime-kuma

by DavidFuchs

Create Maintenance

createMaintenance

Schedules a new maintenance window. During maintenance, the monitors in monitorIDs are suppressed and show MAINTENANCE status instead of DOWN. A window created without monitorIDs suppresses nothing.

Instructions

Schedules a new maintenance window. During maintenance, the monitors in monitorIDs are suppressed and show MAINTENANCE status instead of DOWN. A window created without monitorIDs suppresses nothing. Use strategy "manual" for a window you switch on and off with resumeMaintenance / pauseMaintenance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cronNoCron expression for when the window starts, e.g. "30 3 * * *" (03:30 daily), for the cron strategy
titleYesTitle of the maintenance window
activeNoWhether the window is active (default: true). For a manual window, active means in maintenance right now.
strategyYesScheduling strategy: single=one-time, recurring-interval=every N days, recurring-weekday=specific weekdays, recurring-day-of-month=specific dates, cron=starts on a cron expression and lasts durationMinutes, manual=on whenever active
timezoneNoTimezone the dates and times are in (e.g. "America/New_York", "UTC"). Omit to follow the server timezone.
weekdaysNoDays of week (0=Sunday … 6=Saturday) for recurring-weekday strategy
dateRangeNo[start, end] as local wall-clock times in the window's timezone, e.g. ["2026-10-08T10:00", "2026-10-08T12:00"] — the format Uptime Kuma's own UI stores. Required for single; optional bounds for recurring strategies; ignored for manual.
timeRangeNoDaily [{hours, minutes}, {hours, minutes}] start and end. Required for the recurring-* strategies, ignored otherwise.
monitorIDsNoIDs of the monitors this window suppresses. A window with no monitors suppresses nothing. On update this REPLACES the current list; pass [] to detach all.
daysOfMonthNoDays of month (1-31) for recurring-day-of-month strategy
descriptionNoDescription or reason for the maintenance
intervalDayNoInterval in days for recurring-interval strategy
durationMinutesNoHow long each window lasts, in minutes, for the cron strategy

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
msgNo
monitorIDsNo
maintenanceIDNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.12.0
    • changedInput schema / properties / active / description
      Previous value: -"Whether the window is active (default: true)"New value: +"Whether the window is active (default: true). For a manual window, active means in maintenance right now."
    • addedInput schema / properties / cron
      Added value: +{
      +  "description": "Cron expression for when the window starts, e.g. \"30 3 * * *\" (03:30 daily), for the cron strategy",
      +  "type": "string"
      +}
    • changedInput schema / properties / dateRange / description
      Previous value: -"Date range as [startISO, endISO] (required for single strategy)"New value: +"[start, end] as local wall-clock times in the window's timezone, e.g. [\"2026-10-08T10:00\", \"2026-10-08T12:00\"] — the format Uptime Kuma's own UI stores. Required for single; optional bounds for recurring strategies; ignored for manual."
    • removedInput schema / properties / description / default
      Removed value: -""
    • addedInput schema / properties / durationMinutes
      Added value: +{
      +  "description": "How long each window lasts, in minutes, for the cron strategy",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / monitorIDs
      Added value: +{
      +  "description": "IDs of the monitors this window suppresses. A window with no monitors suppresses nothing. On update this REPLACES the current list; pass [] to detach all.",
      +  "items": {
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / strategy / description
      Previous value: -"Scheduling strategy: single=one-time, recurring-interval=every N days, recurring-weekday=specific weekdays, recurring-day-of-month=specific dates, manual=manually activated"New value: +"Scheduling strategy: single=one-time, recurring-interval=every N days, recurring-weekday=specific weekdays, recurring-day-of-month=specific dates, cron=starts on a cron expression and lasts durationMinutes, manual=on whenever active"
    • changedInput schema / properties / strategy / enum
      Previous value: -[
      -  "single",
      -  "recurring-interval",
      -  "recurring-weekday",
      -  "recurring-day-of-month",
      -  "manual"
      -]New value: +[
      +  "single",
      +  "recurring-interval",
      +  "recurring-weekday",
      +  "recurring-day-of-month",
      +  "cron",
      +  "manual"
      +]
    • changedInput schema / properties / timeRange / description
      Previous value: -"Start and end time within the day as [{hours, minutes}, {hours, minutes}]"New value: +"Daily [{hours, minutes}, {hours, minutes}] start and end. Required for the recurring-* strategies, ignored otherwise."
    • addedInput schema / properties / timeRange / items / properties / hours / maximum
      Added value: +23
    • addedInput schema / properties / timeRange / items / properties / hours / minimum
      Added value: +0
    • changedInput schema / properties / timeRange / items / properties / hours / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / timeRange / items / properties / minutes / maximum
      Added value: +59
    • addedInput schema / properties / timeRange / items / properties / minutes / minimum
      Added value: +0
    • changedInput schema / properties / timeRange / items / properties / minutes / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone (e.g. \"America/New_York\", \"UTC\"). Defaults to server timezone."New value: +"Timezone the dates and times are in (e.g. \"America/New_York\", \"UTC\"). Omit to follow the server timezone."
    • addedOutput schema / properties / monitorIDs
      Added value: +{
      +  "items": {
      +    "type": "number"
      +  },
      +  "type": "array"
      +}
  2. Changed2 schema fields changedv0.11.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.0.0-dev

TDQS

Score is being calculated.