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 paid Cloud plans, including Enterprise.
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, but that does not prevent other administrators with manage_options from managing EMCP.
For rotation, restoration, user changes, and rollout recovery, see Managing a WordPress fleet.
Current fleet boundaries
Section titled “Current fleet boundaries”Initial enrolment is per site. There is no supported bulk onboarding endpoint for independent installations, and settings application through the admin buttons is also per site. Broadcast failures do not undo successful work on other sites.
Start with a representative site, verify its connection and settings, and then expand in paced batches. The fleet guide describes today’s supported workflow.