Requirements and responsibilities
Use a compatible Nginx or OpenLiteSpeed server for native WordPress. Confirm resources for the chosen theme and plugins; native WordPress cannot be created on a Docker server.
Have permission to manage the site, domain/DNS and WordPress administration. Keep the booking administrator and maintenance owner identifiable.
xCloud agent capability boundaries · Easy!Appointments hosting, setup and deployment requirements
WordPress staging requires an eligible paid plan. Validate booking-plugin licensing separately; Site Security PRO is an optional paid protection layer.
xCloud agent capability boundaries · Site Security PRO setup and eligibility
A separate Easy!Appointments deployment needs a compatible Docker server and its own application setup. Read current template requirements rather than assume WordPress hosting also runs the app.
Easy!Appointments hosting, setup and deployment requirements · xCloud agent capability boundaries
Illustrative situation
Illustrative scenario: an agency is launching a salon website for two stylists. The owner needs customers to choose a service and available stylist, receive a booking confirmation, and contact the salon if a booking cannot be completed. This is an acceptance-test example, not a customer case study.
Choose the approach
Choose a WordPress booking plugin only after verifying provider availability, cancellation rules, time zones, required payment or notification integrations, licensing and theme compatibility in the plugin documentation. This guide does not endorse an untested plugin.
Choose a separate Easy!Appointments service when its provider, service and booking model passes the salon tests. Start with a clear booking link from WordPress; embeddings and shared customer records need independent integration verification.
Easy!Appointments hosting, setup and deployment requirements
List deposits, SMS, resource/chair allocation and loyalty as explicit requirements. Do not infer they are provided by the hosting template or its setup wizard.
Easy!Appointments hosting, setup and deployment requirements
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 6
Write the booking acceptance sheet
- Where
- Salon owner and agency planning session
- Permissions
- Authorized site administrator; confirm the selected team and site.
- Inputs
- Services, durations, providers, opening hours, timezone, closure dates and notification expectations.
- Action
- Write one normal booking and one exception for each required rule. Assign the owner to approve the public services, prices, cancellation copy and customer-support route.
- Expected result
- A testable specification and named approver.
- Verify
- For each requirement, identify a plugin/app setting or a documented integration. Mark unknowns before choosing a stack.
- If it fails
- If a must-have rule has no verified implementation, pause the booking commitment and evaluate another documented option.
Sources: Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official initial configuration · Easy!Appointments official application settings
Step 2 of 6
Create the WordPress site and verify its public address
- Where
- xCloud Add site; then the created site overview
- Permissions
- Authorized site administrator; confirm the selected team and site.
- Inputs
- Approved team, compatible server, domain, DNS access and WordPress administrator details.
- Action
- Select WordPress when adding the site, review its server and domain, and submit the approved creation inputs. Wait for provisioning before checking the site URL and HTTPS. Configure DNS through the responsible DNS provider if needed.
- Expected result
- The intended WordPress site opens at the approved HTTPS address.
- Verify
- Check the domain from a separate browser session, certificate validity, administrator login and site identity.
- If it fails
- Inspect the displayed provisioning state and relevant DNS/SSL errors before retrying. Do not create duplicate sites while the original operation is pending.
Sources: xCloud agent capability boundaries
Step 3 of 6
Connect the chosen booking approach
- Where
- WordPress administration or Easy!Appointments administration
- Permissions
- Authorized site administrator; confirm the selected team and site.
- Inputs
- Approved services and provider rules; the selected plugin documentation or the deployed app URL.
- Action
- For the plugin path, install and configure the selected licensed plugin using its own documentation. For the separate-app path, complete its administrator setup and add an explicit Book an appointment link in WordPress. Populate services, assigned providers and working hours in the booking system.
- Expected result
- The public website leads to a usable booking flow with the intended service and provider.
- Verify
- Book a test slot, inspect the administrator record, then attempt an overlapping booking. Check closure dates and timezone presentation.
- If it fails
- If the app permits a prohibited overlap or omits a required rule, revise configuration or selection before publishing booking claims.
Sources: Easy!Appointments hosting, setup and deployment requirements · Manage WordPress core, themes and plugins · Easy!Appointments official initial configuration · Easy!Appointments official application settings
Step 4 of 6
Verify customer communication and dynamic pages
- Where
- WordPress/plugin or app settings; xCloud WordPress Caching where applicable
- Permissions
- Authorized site administrator; confirm the selected team and site.
- Inputs
- Test customer and staff mailboxes, contact form, confirmation messages and dynamic page URLs.
- Action
- Configure the chosen system’s email delivery using its documented provider settings. Submit a contact form and a booking. Review caching settings for booking/account pages; make exclusions in the relevant dashboard or plugin only when the application requires them.
- Expected result
- The correct recipient receives the expected message, and customers see their own current booking state.
- Verify
- Check both inboxes and delivery logs where available. Repeat the flow in two separate private sessions and confirm no customer-specific state leaks between them.
- If it fails
- Treat a saved booking without a delivered confirmation as a failed notification test. Investigate delivery and plugin cache rules before going live.
Sources: xCloud agent capability boundaries · Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official application settings · Easy!Appointments official appointment notifications
Step 5 of 6
Prepare updates, security checks and recovery
- Where
- xCloud WordPress, Site Backup, and Site overview → Add Staging
- Permissions
- Authorized site administrator; confirm the selected team and site.
- Inputs
- Site inventory, current vulnerability findings, backup destination and staging entitlement.
- Action
- Record core/plugin/theme versions. Review vulnerability findings and schedule selected fixes. Confirm a completed backup, prepare eligible staging in the dashboard, and test changes there using the linked update workflow. Document separate backup ownership for any booking app.
- Expected result
- A named owner can repeat maintenance without guessing what must be tested.
- Verify
- Record the completed backup and rehearsal result; repeat booking and form checks after the selected update.
- If it fails
- If no recovery test exists or a staging check fails, hold the production change and resolve it with the responsible maintainer.
Sources: Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud · xCloud agent capability boundaries
Step 6 of 6
Approve launch and transfer responsibilities
- Where
- WordPress public pages, booking administration and client handover
- Permissions
- Authorized site administrator; confirm the selected team and site.
- Inputs
- Acceptance results, maintenance contacts, recovery point and approved launch scope.
- Action
- Publish the booking entry point only after the owner accepts service, availability, notification and cancellation tests. Transfer access through the chosen credential manager and record who handles bookings, WordPress updates, security findings and restores.
- Expected result
- The owner can manage a booking and knows who owns each operational task.
- Verify
- Have a staff member locate and change a test booking; verify the agency can perform maintenance with the agreed permissions.
- If it fails
- If ownership or access is incomplete, retain a staffed contact route and delay the automated booking promise.
Sources: Easy!Appointments hosting, setup and deployment requirements · xCloud agent capability boundaries
Maintenance
Use the linked WordPress update workflow for selected core, theme and plugin changes. Retest the booking entry point, contact form and delivery after changes. Assign a review cadence and owner; a prompt alone does not schedule maintenance.
Manage WordPress updates with Updates Manager · Manage WordPress core, themes and plugins
Review version-based vulnerability findings and unresolved remediation. Decide separately whether paid Site Security PRO is appropriate; virtual patching is not a substitute for updating vulnerable software.
Vulnerability Checker in xCloud · Site Security PRO setup and eligibility
Recovery decisions
Before any WordPress restore, identify bookings or form submissions created after the backup. Obtain an explicit recovery decision and preserve or reconcile newer data with the application owner. Restore from the dashboard, then rerun customer and staff tests.
If using Easy!Appointments, back up its application storage and database together. Docker capture briefly interrupts the app; schedule the window and rehearse recovery before relying on it.
Easy!Appointments hosting, setup and deployment requirements · Back up and restore Docker apps
AI handoff
Connect xCloud MCP in your chosen agent client and select the intended team. Discover the available tools, input schemas and granted scopes. Start with resource reads. Approve a concrete change before each write. If a required tool or permission is missing, continue in the dashboard. The packaged REST fallback accepts GET requests only; do not use it for 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
- Create a WordPress site mcp · write
Requires a compatible Nginx or OpenLiteSpeed server; Docker and single-site agentic servers cannot host a new WordPress site.
Checkpoint: Approve the exact server, domain, capacity, cost and creation inputs before provisioning. Verify completion and HTTPS.
Operation identifiers and scopes to discover
servers.sites.wordpress.create
Scopes: write:sites
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
- Create and synchronize WordPress staging dashboard · manual
WordPress staging requires an eligible paid plan. The API staging-create operation is for Git sites.
Checkpoint: Use Site overview → Add Staging and staging Site → Manage Staging. Inspect push/pull scope before overwriting data.
- Configure native WordPress backup and restore dashboard · manual
Native schedule, retention and destination changes and all restores are dashboard-only.
Checkpoint: Use Site → Site Backup. Before restoring, confirm backup, target, scope and treatment of newer records.
- Configure WordPress caching dashboard · manual
Cache settings reads and purges do not allow changing cache layers or exclusions. OpenLiteSpeed page exclusions live in the LiteSpeed Cache plugin.
Checkpoint: Use Site → WordPress → Caching or the relevant plugin. Test dynamic booking, checkout and account pages in separate sessions.
- Configure the booking application and run acceptance tests app · manual
xCloud hosting operations do not configure business rules, staff calendars, reminders, payments or WordPress plugins.
Checkpoint: An authorized application administrator performs configuration and confirms each customer and staff journey.
Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official initial configuration · Easy!Appointments official application settings · Easy!Appointments official appointment notifications · xCloud MCP documentation and connection profiles
Copyable agent brief
Manual checkpoints
- Choose and configure the booking plugin or application with its administrator.
- Create WordPress staging, inspect cache exclusions and perform restores in the dashboard.
- The salon owner accepts booking, cancellation and notification results and the recovery plan.
Feature coverage
- launch (covered): Provision and validate the WordPress address. Create the WordPress site and verify its public address
- updates-security-staging (covered): Use selected updates with a backup, staged checks and vulnerability review. Prepare updates, security checks and recovery
- backups-recovery (covered): Account for WordPress and separate booking data before a restore. Prepare updates, security checks and recovery
- performance (covered): Verify dynamic-page caching isolation rather than promise a speed score. Verify customer communication and dynamic pages
- business-validation-handover (covered): Owner validates real customer and staff journeys. Connect the chosen booking approach Verify customer communication and dynamic pages Approve launch and transfer responsibilities
Sources
- xCloud agent capability boundaries
- Easy!Appointments hosting, setup and deployment requirements
- Site Security PRO setup and eligibility
- Manage WordPress core, themes and plugins
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Back up and restore Docker apps
- Easy!Appointments official initial configuration
- Easy!Appointments official application settings
- Easy!Appointments official appointment notifications
- xCloud MCP documentation and connection profiles