Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: An agency puts several WordPress sites on one server.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Shared resource spikes can affect unrelated clients.
Illustrative situation
Illustrative scenario, not a customer case study: An agency puts several WordPress sites on one server. CPU, RAM, disk and key user journeys remain acceptable under representative load.
Choose the approach
Choose capacity based on peak overlap and actual resource trends. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
List sites, traffic windows and critical tasks
- Where
- xCloud team/site resource read and planning sheet
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- List sites, traffic windows and critical tasks; exact site identity, named approver and controlled sample data.
- Action
- List sites sharing the server, each site's busy period, disk growth and the most important user transaction.
- Expected result
- Capacity review has workload context.
- Verify
- Capacity review has workload context. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a site is missing from inventory, correct the server/site map.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
Step 2 of 5
Inspect server resource and disk history
- Where
- xCloud team/site resource read and planning sheet
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Inspect server resource and disk history; exact site identity, named approver and controlled sample data.
- Action
- Read xCloud CPU, RAM, disk and PHP worker history for peak periods; record the measurement window and any alerts.
- Expected result
- Resource patterns are visible, not guessed.
- Verify
- Resource patterns are visible, not guessed. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If metrics are unavailable, mark uncertainty and gather measurements.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
Step 3 of 5
Estimate combined peak and growth headroom
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Estimate combined peak and growth headroom; exact site identity, named approver and controlled sample data.
- Action
- Estimate combined peak overlap and remaining headroom; compare WordPress background tasks and backup windows.
- Expected result
- The agency has a concrete capacity hypothesis.
- Verify
- The agency has a concrete capacity hypothesis. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If peaks coincide, avoid adding another site before evaluating scale options.
Sources: WordPress roles and capabilities · xCloud agent capability boundaries
Step 4 of 5
Run representative traffic tests without harming live users
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Run representative traffic tests without harming live users; exact site identity, named approver and controlled sample data.
- Action
- Run a safe representative traffic test on non-production or use observed production trends, checking business path latency and error rate.
- Expected result
- The chosen evidence reflects user impact.
- Verify
- The chosen evidence reflects user impact. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a test would harm live customers, use a controlled test environment.
Sources: WordPress roles and capabilities · xCloud agent capability boundaries
Step 5 of 5
Set thresholds, owner and migration trigger
- Where
- xCloud team/site resource read and planning sheet
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Set thresholds, owner and migration trigger; exact site identity, named approver and controlled sample data.
- Action
- Set a measured threshold and owner for resizing or moving a site, with a separate approved change plan.
- Expected result
- Growth has a trigger, not a vague promise.
- Verify
- Growth has a trigger, not a vague promise. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- Do not resize resources based on one transient spike alone.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: CPU, RAM, disk and key user journeys remain acceptable under representative load. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
This review does not change production settings. Keep the original measurements and configuration, then write a separately approved experiment and rollback criterion before any cache, PHP or capacity change.
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
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
- Review a WordPress business journey app · manual
Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence.
Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision.
Copyable agent brief
Manual checkpoints
- The named site, business or provider owner supplies application evidence the connected hosting reads cannot observe.
- A separately approved operator performs any later configuration, staging, update, restore or publication described in the decision sheet.
- The owner accepts the review finding and proposed checks without treating the unexecuted change as completed.
Feature coverage
- business-acceptance (covered): CPU, RAM, disk and key user journeys remain acceptable under representative load. Run representative traffic tests without harming live users
- recovery (covered): Shared resource spikes can affect unrelated clients. Set thresholds, owner and migration trigger