Requirements and responsibilities
Name the team, server, hostname, owner and affected users for the WordPress site. 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 · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
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 · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
For WordPress, verify the file and database backup scope and a safe target for recovery. Native scheduling, destination settings, staging synchronization and restore remain dashboard actions. 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 · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
A clone or recovered database may start scheduled jobs and carry live payment, booking, mail or webhook credentials. Arrange provider or network controls that prevent external side effects before the copied application can run. If the current xCloud flow cannot guarantee that isolation, use a sanitized fixture or postpone the clone; changing credentials after startup may be too late.
Create a staging environment in xCloud · xCloud agent capability boundaries
Illustrative situation
A WordPress staging site was cloned months ago and may still point at live booking and email services. The operator audits its separation before testers use it again.
Choose the approach
A different URL is necessary but insufficient: app credentials, indexing, webhook and outbound mail also matter.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
Any push/pull action is a separate change that can overwrite newer production data.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Map environments
- Where
- xCloud Sites and WordPress settings
- Permissions
- Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
- Inputs
- Production/staging IDs, URLs, clone time
- Action
- Confirm which site is production and which is staging. Record versions and domains and test signed-out routes.
- Expected result
- An unambiguous environment map.
- Verify
- Compare dashboard IDs and WordPress site URLs.
- If it fails
- If identities are unclear, prohibit synchronization until resolved.
Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Create a staging environment in xCloud
Step 2 of 5
Check access and indexing
- Where
- Staging WordPress and external browser
- Permissions
- Authorized WordPress/WooCommerce application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Test account, robots state, basic access
- Action
- Verify staging requires intended access and inspect actual search-engine visibility and public links. Do not assume xCloud sets noindex constants.
- Expected result
- A private test environment.
- Verify
- Open staging in a signed-out session and inspect response metadata.
- If it fails
- If staging is public or indexable unintentionally, restrict it before test data use.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud
Step 3 of 5
Inspect integration endpoints
- Where
- Staging plugin settings and providers
- Permissions
- Authorized WordPress/WooCommerce application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Payment keys, SMTP, booking calendar, webhooks
- Action
- Compare staging credentials and endpoint URLs with production. Replace or disable live side effects using app admin controls.
- Expected result
- A sandboxed integration map.
- Verify
- Submit a harmless test and check only test recipients/systems.
- If it fails
- If any live effect occurs, stop tests and investigate affected records.
Sources: Manage WordPress plugins · Create a staging environment in xCloud
Step 4 of 5
Check data freshness and push scope
- Where
- xCloud Manage Staging; WooCommerce if used
- Permissions
- Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
- Inputs
- Clone time, current production records, sync direction
- Action
- Read available push/pull options and note data classes that have changed since clone, especially orders, bookings and members.
- Expected result
- A safe synchronization recommendation.
- Verify
- Compare recent production IDs to staging.
- If it fails
- If staging DB is older, prohibit database push without reconciliation.
Sources: Create a staging environment in xCloud · xCloud agent capability boundaries
Step 5 of 5
Record operating rules
- Where
- Staging runbook and agency ticket
- Permissions
- Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
- Inputs
- Refresh cadence, owners, allowed test data
- Action
- Document who can refresh, push or pull staging and which integrations must be isolated after every clone.
- Expected result
- An auditable separation policy.
- Verify
- Have a tester verify the checklist before next use.
- If it fails
- If isolation cannot be guaranteed, retire the stale copy and create a fresh safe staging site.
Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Create a staging environment in xCloud
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 · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
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 · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
Recovery decisions
If staging sends to a live provider, stop the integration, identify affected recipients and records, and have its owner correct them in the provider or application.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
Rebuild or refresh the isolated staging copy only after suppressing side effects; check newer production records before any push or pull.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Manage WordPress core, themes and plugins · Site backups in xCloud · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · Create a staging environment in xCloud
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
- staging-audit decision, evidence and task action (covered): The procedure identifies the authorized task boundary and observable result. Map environments Check access and indexing Inspect integration endpoints Check data freshness and push scope
- backup, ongoing operation and recovery (covered): Recovery and maintenance are checked in the task procedure. Check data freshness and push scope Record operating rules