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: A clinic's public WordPress pages should direct visitors to an independently run appointment service.
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: WordPress hosting cannot configure external availability or reminder rules.
Illustrative situation
Illustrative scenario, not a customer case study: A clinic's public WordPress pages should direct visitors to an independently run appointment service. A visitor books once and staff see the same appointment in the service.
Choose the approach
Choose a plain link unless an embed or shared login is explicitly supported and tested. 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 · Easy!Appointments hosting, setup and deployment requirements
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
Define booking data ownership
- Where
- WordPress or selected plugin/app administrator
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Define booking data ownership.
- Action
- Specify what WordPress publishes and what the scheduler stores: service, staff, availability, customer contact and cancellation data. Decide whether a plain link meets the need.
- Expected result
- Website and scheduler responsibilities are clear.
- Verify
- The owner names the system of record for one appointment.
- If it fails
- If both systems would edit availability, choose one source before launch.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Provision separate services
- Where
- xCloud Add site and site overview
- Permissions
- Named xCloud team/site administrator; verify the exact target.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Provision separate services.
- Action
- Create native WordPress on a compatible server and choose a separately documented scheduler deployment. Confirm the scheduler's server, template and administrator requirements.
- Expected result
- Both applications have approved addresses and owners.
- Verify
- Open both URLs and record where booking data lives.
- If it fails
- If the scheduler is unavailable for this stack, choose a supported dashboard option or revise the design.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
Step 3 of 5
Configure availability in the app
- Where
- Easy!Appointments administrator
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Configure availability in the app.
- Action
- In scheduler administration set services, providers, hours, closures and message rules using its vendor guide. Add a clear booking link and support route in WordPress.
- Expected result
- Visitors can discover a usable scheduler.
- Verify
- Compare link target and one service-provider combination with the approved plan.
- If it fails
- If an embed or shared login fails across browsers, retain the plain link.
Sources: Easy!Appointments official initial configuration · Easy!Appointments official application settings
Step 4 of 5
Test customer and staff states
- Where
- WordPress public pages and relevant external provider
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Test customer and staff states.
- Action
- As a test customer book, cancel and try an occupied slot. Ask staff to find the appointment; check confirmation delivery separately.
- Expected result
- Both sides observe one consistent appointment state.
- Verify
- Match time, service and provider in the customer message and administrator record.
- If it fails
- If staff cannot see a booking or a conflict is allowed, correct app rules before announcing online booking.
Sources: WordPress roles and capabilities · Easy!Appointments official initial configuration · Easy!Appointments official application settings
Step 5 of 5
Protect both data stores
- Where
- xCloud Docker Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; verify the exact target.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Protect both data stores.
- Action
- Assign update and backup owners for WordPress and the scheduler separately. Include booking records in recovery planning.
- Expected result
- Each service has a named operator and recoverable point.
- Verify
- Inspect both completed backup records and compare timestamps with a newer test booking.
- If it fails
- Never restore older scheduler data over new appointments without an approved reconciliation process.
Sources: Back up and restore Docker apps · xCloud agent capability boundaries
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: A visitor books once and staff see the same appointment in the service. 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
Keep WordPress content and the separate Easy!Appointments database/storage in distinct backup plans. Before any scheduler restore, compare its point with newer bookings and reconcile them with the app owner; a native WordPress restore does not recreate scheduler records.
Back up and restore Docker apps · Easy!Appointments hosting, setup and deployment requirements
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
- Configure WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
- 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
- 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
- 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.
- Create and inspect Docker backups mcp · write
Backup capture briefly stops the app. Use supported local, S3-compatible or SFTP storage; the packaged REST wrapper is GET-only.
Checkpoint: Confirm site, storage, retention and the interruption window before creating a backup or changing settings. Check terminal completion.
Operation identifiers and scopes to discover
sites.docker.backup, sites.docker.backups, sites.docker.backupSettings.update
Scopes: read:sites, write:sites
Docker backup operations and storage constraints · Back up and restore Docker apps
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: In scheduler administration set services, providers, hours, closures and message rules using its vendor guide. Add a clear booking link and support route in WordPress.
- The business owner compares the controlled sample with this observable result: Both sides observe one consistent appointment state.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): A visitor books once and staff see the same appointment in the service. Test customer and staff states
- recovery (covered): WordPress hosting cannot configure external availability or reminder rules. Protect both data stores
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- Easy!Appointments hosting, setup and deployment requirements
- 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
- Docker backup operations and storage constraints