Requirements and responsibilities
Name the team, server, hostname, owner and affected users for the Uptime Kuma application. Record the current version and the actual business flow that must survive the change. Confirm the current dashboard form, plan eligibility, and server capacity before committing a resource change. A one-click catalog listing is discovery, not permission or proof that the connected MCP profile can install it.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Prepare a non-sensitive test input and an acceptance record. Keep access to the app administrator and an independent observer where possible; omit secrets from AI prompts and client reports.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
For a Docker app, identify persistent volumes, bind mounts, external databases and app-level export requirements. A Docker backup briefly stops the app, and an in-place restore replaces current state. Agree a maintenance window and owner before any action that interrupts the service or overwrites data.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Illustrative situation
A WordPress checkout occasionally fails while the homepage remains up. The owner wants Uptime Kuma to alert on an external endpoint and document its limits.
Choose the approach
Place the monitor outside the failure domain where practical; a monitor on the same unavailable server can miss an outage.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
HTTP availability of one page is not proof of checkout success; define any deeper synthetic check separately.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Choose a meaningful target
- Where
- WordPress business journey and DNS
- Permissions
- Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
- Inputs
- Public URL, expected status, maintenance windows
- Action
- Pick a stable HTTPS URL whose failure signals a real user problem. Decide whether a separate task-specific checkout probe is needed.
- Expected result
- A monitor target and expected response.
- Verify
- Open it without a logged-in session and verify status.
- If it fails
- If it is cached while checkout fails, do not use it as the sole health signal.
Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Uptime Kuma notification methods
Step 2 of 5
Deploy the monitor
- Where
- xCloud One-Click Apps and DNS
- Permissions
- Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
- Inputs
- Uptime Kuma template, Docker server, hostname
- Action
- Install Uptime Kuma on a compatible server, preferably outside the WordPress server. Secure its administration URL.
- Expected result
- A reachable monitoring application.
- Verify
- Sign in over HTTPS and confirm monitor host location.
- If it fails
- If no independent host is available, document correlated-failure risk.
Sources: xCloud One Click Apps catalog · xCloud agent capability boundaries
Step 3 of 5
Configure check and alert
- Where
- Uptime Kuma monitor and notification settings
- Permissions
- Authorized Uptime Kuma application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- URL, interval, timeout, channel recipient
- Action
- Create an HTTPS monitor with agreed interval and response expectations. Add the real on-call notification channel in the app.
- Expected result
- A configured check and alert route.
- Verify
- Use the app's test-notification control and inspect recipient delivery.
- If it fails
- If notification fails, repair it before treating the monitor as operational.
Sources: Uptime Kuma notification methods
Step 4 of 5
Exercise failure behavior
- Where
- Dedicated test endpoint or approved maintenance mode
- Permissions
- Authorized Uptime Kuma application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Test window, on-call participant
- Action
- Use a dedicated probe endpoint to create a safe failure, or an explicitly approved maintenance window; do not break the production checkout. Observe down, recovery and silence behavior.
- Expected result
- A proven escalation path without noisy false alarms.
- Verify
- Compare event timestamps to received notifications.
- If it fails
- If no alert arrives or it is delayed beyond tolerance, adjust configuration and repeat.
Sources: Uptime Kuma notification methods
Step 5 of 5
Document coverage and backup
- Where
- Monitor inventory and xCloud Docker Backup
- Permissions
- Authorized xCloud team/site operator with the discovered write scope for this exact operation and owner approval for its target and interruption.
- Inputs
- Monitors, recipients, backup row, escalation owner
- Action
- Record which WordPress flows are covered, which are not, and who updates monitors when URLs change. Check a completed app backup.
- Expected result
- A maintained monitoring runbook.
- Verify
- Have a second person identify the next alert recipient and backup.
- If it fails
- If Uptime Kuma is itself down, ensure an independent host-level signal exists.
Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Uptime Kuma notification methods
Maintenance
Review this task after app or template updates and at the cadence agreed with the owner. Record failures as dated observations rather than assuming host health proves service health.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Watch access changes, backup completion, free storage and external providers. Recheck integrations after credential, DNS, mail or source-data changes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Recovery decisions
If an alert is missing or false, inspect monitor target, retries and notification route; confirm the real recipient can receive a controlled test message.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Use another independent signal until monitoring is repaired. Restore monitor app state only if its data is damaged and verify notification routing afterward.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Uptime Kuma notification methods · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
AI handoff
Connect an authorized xCloud MCP profile and discover its exact tools and team scope. The packaged REST wrapper is GET-only; use dashboard or app controls for undocumented writes.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
Copyable agent brief
Manual checkpoints
- Approve exact site, target, cost and any write or maintenance window after inspecting the proposed plan.
- An authorized Uptime Kuma administrator must configure and test app users, content, integrations and business rules in the app.
- Native WordPress staging, backup schedule/settings, push/pull and all restores are dashboard-only; Docker restore is dashboard-only and replaces state.
- Reconcile data created after the chosen recovery point before any destructive restore.
Feature coverage
- monitor decision, evidence and task action (covered): The procedure identifies the authorized task boundary and observable result. Choose a meaningful target Deploy the monitor Configure check and alert Exercise failure behavior
- backup, ongoing operation and recovery (covered): Recovery and maintenance are checked in the task procedure. Exercise failure behavior Document coverage and backup