Cloud features and services
Hosted multi-site Gateway
Section titled “Hosted multi-site Gateway”Add one remote MCP connection to your AI client and route calls to the WordPress sites connected to your Cloud workspace. Gateway is included on every Cloud plan, up to the plan’s connected-site limit (Free covers 3 sites).
Choose a site by UUID or URL. site: "all" broadcasts to all Gateway-connected sites; write broadcasts require a workspace opt-in and per-call confirmation. Results identify individual successes and failures. There is currently no selected-subset parameter or durable job-resume token.
Each site authorizes access separately and issues a revocable OAuth credential tied to a WordPress user. Gateway does not host your WordPress site or grant tools beyond that site’s configuration and permissions. Set up Gateway.
Sandbox artifact storage
Section titled “Sandbox artifact storage”Back up supported Sandbox blocks, widgets, and PHP snippets to your Cloud library, then pull them onto a connected site. Pulled artifacts are imported as new inactive drafts for review.
This is reusable-artifact storage, not a whole-site backup, database snapshot, or disaster-recovery service. Available artifact kinds and capacity depend on the plugin and Cloud entitlements. Read the backup and pull tool reference.
Settings sync
Section titled “Settings sync”On paid Cloud plans, use the Connection screen’s Push settings to cloud and Pull settings from cloud buttons to collect and apply supported EMCP preferences across sites in the same workspace.
The shared settings bundle includes preferences such as tool toggles, active modules, and context settings. It excludes licence activation and connection credentials. Review the default allowlist before a rollout.
The lower-level cloud-config-sync MCP tool stores or retrieves a supplied blob. It does not automatically apply settings to WordPress. Brand-kit and lower-level tool-toggle blobs use site scope. Read the examples and scope rules.
Marketplace
Section titled “Marketplace”Browse reusable artifacts through the Marketplace and install supported listings into the site’s Sandbox as inactive drafts. Access to paid listings depends on Cloud entitlement. Publishing and updating your own listings uses the Sandbox and Marketplace workflow, including review where required.
Explore Marketplace tools and screens.
Connection management
Section titled “Connection management”Review your connected sites in Cloud, inspect Gateway targets from your AI client, and revoke a connection from the site or Cloud. A dedicated WordPress administrator can be used as the execution identity. Plugin 3.19.0 also provides a site-local Management access policy for limiting EMCP administration to selected administrators. This policy is separate from the WordPress user and capabilities used by Gateway.
For rotation, restoration, user changes, and rollout recovery, see Managing a WordPress fleet.
Fleet health, onboarding, and configuration
Section titled “Fleet health, onboarding, and configuration”The Account interface has dedicated Fleet health, Bulk onboarding, and Configuration pages. Fleet health supports selected-site background checks, saved groups, schedules, and dashboard failure and recovery alerts. Groups organize sites; they do not restrict a member’s access to one fleet.
Bulk onboarding and managed configuration require a paid Cloud plan, workspace-owner access, and plugin 3.19.0 or later on the sites you manage. Each account page includes a quick-start guide and a link to the complete workflow.
Workspace owners can create short-lived enrollment grants for independent installations and use WP-CLI with a chosen WordPress administrator. Gateway access requires explicit consent. Managed configuration supports previews of supported EMCP settings and separately approved background deployment, with a canary before the remaining sites, durable operation receipts, and conflict-aware rollback. A configuration review accepts at most ten sites; secrets, licensing, site identity, free-text context, and the management access policy are excluded.
Start with a representative site, verify its connection and settings, and expand in paced batches. New Enterprise licenses include 250 sites; existing licenses retain their purchased allowance. Site capacity is not a guarantee of simultaneous enrollment or request throughput. Broadcast failures do not undo successful work on other sites. See the fleet guide and configuration workflow.
Safe WordPress updates
Section titled “Safe WordPress updates”On supported installations with the Cloud Safe Updates plugin tool, workspace owners can review a plugin, theme, or WordPress update queue. Each group gets a file and database snapshot, followed by repeated live checks. A failed group stops the queue and is restored; linked dependencies can update together before the group is checked.
Updates use a maintenance window on the existing site. The checks detect HTTP/PHP failures and substantial missing content; they do not compare screenshots or test checkout transactions. The plugin tool and hosting prerequisites are required in addition to Gateway access. Read the safe updates guide before starting.
