Book a demo
Book a demo
Login

App workflow WordPress

Create a WordPress maintenance report for a client

Generate the documented report and explain included signals, timeframe, and omissions. Check the named site's prerequisites, task result, backup scope and recovery handoff with xCloud.

Technical review: · Source reviewed; no production deployment test claimed

Published · Updated · xCloud editorial

Read this guide as Markdown

Requirements and responsibilities

Illustrative situation

An agency owes a monthly maintenance readout for a client WordPress site. It must separate verified changes from scheduled work and unresolved risks before sharing it.

Choose the approach

Dashboard and application procedure

Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.

Step 1 of 5

Define client and period

Where
Agency contract and xCloud team
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Client site IDs, reporting dates, recipients
Action
Confirm which WordPress sites belong to the client, the reporting window and who is authorized to receive security details.
Expected result
A bounded report scope.
Verify
Cross-check domains against the contract and team inventory.
If it fails
If ownership is ambiguous, hold the report until the client confirms scope.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries

Step 2 of 5

Collect change evidence

Where
xCloud Updates Manager and site history
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Update history, component versions, incident tickets
Action
List applied updates with dates, before/after versions and actors. Match incidents and staging tests to each material change.
Expected result
A change log that can be checked against source records.
Verify
Spot-check one update against current WordPress version.
If it fails
If history is incomplete, mark the gap rather than claiming no changes.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Manage WordPress updates with Updates Manager · Create a staging environment in xCloud

Step 3 of 5

Check backup and security state

Where
xCloud Site Backup and Vulnerability Scan
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Completed rows, failures, open findings
Action
Record latest completed file/database backup, failed jobs, scan date and open findings with assigned owner and due date.
Expected result
An operational status section grounded in observed rows.
Verify
Verify backup completion and finding version on the named site.
If it fails
If a backup failed or scan is stale, state it clearly and assign remediation.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Vulnerability Checker in xCloud · Site backups in xCloud

Step 4 of 5

Prepare the dashboard report

Where
xCloud WordPress maintenance report
Permissions
Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
Inputs
Selected sites, period, recipient settings
Action
Use the dashboard report flow, review generated sections, add concise explanations for exceptions and verify period/site mapping.
Expected result
A draft client report.
Verify
Compare every highlighted claim with collected evidence.
If it fails
If the report merges wrong sites or hides failures, correct it before sharing.

Sources: WordPress website maintenance reports for clients · xCloud agent capability boundaries

Step 5 of 5

Review and deliver safely

Where
Agency reviewer and approved client channel
Permissions
Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
Inputs
Draft, client contacts, sensitive details
Action
Have a second reviewer check accuracy and recipients. Share through the authorized channel and retain a dated copy with follow-up tasks.
Expected result
A truthful maintenance handoff.
Verify
Confirm recipient and next review date with the client contact.
If it fails
If sensitive details went to the wrong audience, follow incident handling rather than re-sending blindly.

Sources: WordPress website maintenance reports for clients · xCloud agent capability boundaries

Maintenance

Recovery decisions

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 WordPress 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

Sources

Continue

Explore all use cases