Requirements and responsibilities
Name the team, server, hostname, owner and affected users for the Umami 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 · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · 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 · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · 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 · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Illustrative situation
A WordPress publisher wants private traffic reports on a separate hostname. The team must choose Umami or Matomo, install a tracker and prove one controlled visit is counted.
Choose the approach
Umami uses its own website and script setup; Matomo has a different tracking-code and database/config backup model.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Consent, internal-traffic exclusions and retention policy are owner decisions; self-hosting alone does not settle them.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · 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 analytics model
- Where
- Umami and Matomo upstream docs
- Permissions
- Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
- Inputs
- Required metrics, data retention, database capacity
- Action
- Compare needed events, reporting access and backup requirements. Select one current xCloud template and document why it fits.
- Expected result
- A specific service and measurement owner.
- Verify
- Confirm app template availability and data/storage needs.
- If it fails
- If the selected template lacks required features, revisit choice before install.
Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Back up and restore Docker apps · Umami tracking setup
Step 2 of 5
Deploy a separate service
- 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
- Analytics hostname, Docker server, app template
- Action
- Install the chosen app on a compatible server, attach HTTPS and record its first-run URL for the authorized application owner. Keep WordPress unchanged.
- Expected result
- A reachable analytics admin page.
- Verify
- Check URL, certificate and app version.
- If it fails
- If Umami is the chosen dashboard-only template, do not claim MCP can install it.
Sources: xCloud One Click Apps catalog · xCloud agent capability boundaries
Step 3 of 5
Create the site property
- Where
- Analytics app administrator
- Permissions
- Authorized Analytics application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- WordPress canonical domain, property name, access role
- Action
- Complete the selected app first administrator setup, add the WordPress website property and generate its tracker or tag. Limit report access to approved users.
- Expected result
- A property with a known site ID or tracking code.
- Verify
- Verify the tracker matches the production hostname.
- If it fails
- If the tracker points to staging, correct it before interpreting reports.
Sources: Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving
Step 4 of 5
Install and test tracker
- Where
- WordPress plugin/theme or tag manager; browser network view
- Permissions
- Authorized Analytics application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Tracking snippet, test page, consent state
- Action
- Add the selected tracker through an approved WordPress integration. Visit a public page with a consent state consistent with policy, then inspect network request and report.
- Expected result
- One controlled visit or event appears in the chosen property.
- Verify
- Compare request timestamp, hostname and analytics event count.
- If it fails
- If absent, check script loading, blocker/consent, property ID and service reachability separately.
Sources: Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving
Step 5 of 5
Set operations and retention
- Where
- Analytics admin 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
- Internal traffic rule, data retention, database backup
- Action
- Decide exclusion of team traffic, report access, data deletion and backup scope. For Matomo include database/config/plugins; for Umami inspect its database and persistent paths.
- Expected result
- Reports with understood scope and recoverable data.
- Verify
- Repeat a test after filtering, and check completed backup.
- If it fails
- If analytics data cannot be restored or policy is unclear, keep reports labeled experimental.
Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Umami tracking setup · Matomo application and data backup
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 · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · 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 · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Recovery decisions
Before data recovery, identify incident time, completed backup, target and records created after the snapshot. Preserve current evidence and live data before replacement.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Use the documented dashboard or application recovery procedure with the authorized owner. Repeat the task-specific limited-user check; reconcile newer records before reopening writes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Umami tracking setup · Umami event tracking · Matomo tracking code for WordPress · Matomo application and data backup · Matomo report auto-archiving · 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 Umami 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
- analytics decision, evidence and task action (covered): The procedure identifies the authorized task boundary and observable result. Choose analytics model Deploy a separate service Create the site property Install and test tracker
- backup, ongoing operation and recovery (covered): Recovery and maintenance are checked in the task procedure. Install and test tracker Set operations and retention
Sources
- xCloud agent capability boundaries
- xCloud MCP documentation and connection profiles
- Umami tracking setup
- Umami event tracking
- Matomo tracking code for WordPress
- Matomo application and data backup
- Matomo report auto-archiving
- Back up and restore Docker apps
- Docker backup operations and storage constraints
- xCloud One Click Apps catalog