EMCP Cloud & Marketplace

New in v3.8.0. Connect this site to your EMCP Cloud account (EMCP Tools → Connection, Cloud section, Connect to EMCP Cloud) to back up Sandbox artifacts, pull them onto other connected sites, and browse or install what other people have published to the Marketplace. Availability depends on the operation: configuration sync requires a paid Cloud plan. These tools require the EMCP Cloud module and an active Cloud connection. Both halves below are registered by the same class and gated the same way, so one page covers both. The Marketplace screen in wp-admin is a dedicated browsing surface, not a different system.

These 7 tools always registered and worked, but had no entry on the Tools screen until v3.13.0, so before that you couldn’t toggle one off individually. They now live in the EMCP Cloud and Marketplace sections of the EMCP Modules tab on EMCP Tools → Tools. See Disabling individual tools.

Backup & sync

Looking for plugin, theme, or WordPress updates? See the Safe Updates guide for plugin setup, Cloud account screens, screenshots, and recovery instructions. Safe Updates uses its own temporary recovery snapshots, separate from the Sandbox artifact backup tools below.

emcp-tools/cloud-status

Returns the plan, limits, and usage for the connected account. Read-only.

emcp-tools/cloud-backup

Backs up a local Sandbox artifact to your Cloud account.

Input: kind (required): block, widget, or snippet. id (required): the artifact’s local post ID.

emcp-tools/cloud-list

Lists the artifacts backed up to your Cloud account, optionally filtered by kind. Read-only.

emcp-tools/cloud-pull

Pulls a Cloud artifact into this site by UUID. Imported as a new inactive draft, same review gate as everything else in the Sandbox.

Input: artifact_uuid (required), kind (optional).

emcp-tools/cloud-config-sync

Pushes or pulls a config blob, one of settings, brand_kit, or tool_toggles, between this site and your Cloud account. This is the mechanism behind Settings Sync (a paid Cloud feature): copying tool toggles, active modules, Compact tool mode, and other behavior preferences between connected sites.

As of v3.15.1, the Settings Sync buttons (Push settings to cloud / Pull settings from cloud in the Cloud section of EMCP Tools → Connection) store the curated settings bundle at account scope. A push from one connected site can therefore be pulled by another site in the same Cloud workspace. Brand kits, tool toggles sent through the lower-level config tool, and other configuration types retain their existing site scope. Secrets, provider API keys, and Cloud connection credentials are never included.

The plugin and Cloud website can be updated in either order. A new plugin uses the stronger site-registration proof when the website supplies one and accepts the older registration response when it does not. Existing connections remain valid during the rollout; updating does not require every connected site to reconnect at once.

Input: type (required): settings / brand_kit / tool_toggles. direction (required): push or pull. data (required when pushing).

Retrieving a blob is not applying settings

cloud-config-sync is a storage operation. On push, supply data explicitly: the tool does not collect local options for you, and the current handler uploads an empty array when data is omitted. On pull, the result contains the stored data as a JSON string; the tool does not write that data into WordPress options.

To copy supported preferences using the admin UI, use Push settings to cloud on the source site, then Pull settings from cloud on each destination site. Those buttons collect and apply the curated bundle. There is currently no equivalent fleet-wide apply operation in cloud-config-sync.

Type	Scope used by the plugin	What a pull returns
settings	Shared by sites in the same Cloud workspace	The workspace settings blob
brand_kit	Calling site’s UUID	That site’s brand-kit blob
tool_toggles	Calling site’s UUID	That site’s tool-toggle blob

A settings push replaces the shared blob. Choose one source site for a rollout; pushing different settings from every site does not merge them.

Examples

Arguments for a direct call to emcp-tools/cloud-config-sync that stores a supplied preference:

{
  "type": "settings",
  "direction": "push",
  "data": { "emcp_tools_strict_schemas": true }
}

Arguments to retrieve the shared blob through Gateway from one connected site (replace the example URL with a URL returned by emcp_list_sites):

{
  "site": "https://example.com",
  "type": "settings",
  "direction": "pull"
}

Gateway also accepts site: "all". This tool is classified as a write for both directions, so even a broadcast pull requires Allow broadcast writes and confirm: true:

{
  "site": "all",
  "type": "settings",
  "direction": "pull",
  "confirm": true
}

This returns results from the connected sites; it does not apply settings to them. There is no site-array or selected-subset parameter. See fleet operations and recovery.

Settings included by the admin sync buttons

The default allowlist is:

• emcp_tools_disabled_tools and legacy elementor_mcp_disabled_tools
• emcp_tools_active_modules
• emcp_tools_dispatcher_mode
• emcp_tools_strict_schemas
• emcp_tools_content_mirror_enabled
• emcp_tools_site_context, emcp_tools_site_context_enabled, and emcp_tools_context_sections
• emcp_tools_module_themer_force_render
• emcp_tools_memory_require_approval and emcp_tools_memory_auto_summarize

Only stored keys are collected. Applying a bundle updates included, allowlisted keys; it does not reset absent keys. The emcp_tools_settings_sync_keys PHP filter can customize the allowlist, so site-specific extensions may change it.

The built-in bundle excludes licence keys and activation state, provider API keys, OAuth tokens, Cloud connections, site UUIDs, site profiles, and audit logs. Synchronizing settings does not activate Pro or enrol a site in Gateway. Review site context before sharing it, since its free-text instructions may be specific to the source site.

The lower-level blob tool accepts caller-supplied data. Do not put credentials in data; arbitrary fields neither activate licences nor provision connections.

Marketplace

emcp-tools/cloud-marketplace-list

Browse published Marketplace listings (blocks, widgets, snippets), optionally filtered by category. Read-only.

emcp-tools/cloud-marketplace-install

Installs a Marketplace listing by slug. Imported as a new inactive draft; review and activate it like any other Sandbox artifact. Installs made this way also show as “Installed” on the Marketplace screen.

Input: slug (required).

Publishing your own artifacts to the Marketplace, and the Save to Cloud / Cloud library / Push update to Marketplace actions, live on the Sandbox admin screens. They are not separate MCP tools: they call the same backup/pull mechanism above under the hood.

The Marketplace screen

EMCP Tools → Library → Marketplace (admin.php?page=emcp-tools-marketplace) shows while the EMCP Cloud module is on. Until the site is connected it shows “Connect this site to EMCP Cloud” with Connect to EMCP Cloud.

• Type tabs with counts: All / Widgets / Blocks / Snippets / Templates.
• Filters apply as you change them: Search items…, a Category menu, access All / Free / Pro, Sort (Newest, Most installed) and Verified authors only. Active filters show as removable chips with Clear all. Switch between Grid view and List view.
• Each card shows the name and author (with a “Verified author” mark) and an Install button, or “Installed” with a link to review it. Pages hold 20 listings.
• Install lands the item as an inactive draft in the Sandbox for you to review and activate. A paid item needs a paid Cloud plan.
• My installs lists what you installed from the Marketplace, each with a review link. Publish to Cloud takes you to the Sandbox, where you publish items from each row’s menu.

The general export/import mechanism

Two tools, free tier, no Cloud connection required: emcp-tools/export-sandbox-artifact and emcp-tools/import-sandbox-artifact. These package a block/widget/snippet as a portable, checksum-verified bundle, the same shape cloud-backup/cloud-pull use internally, and are also what the Sandbox admin screens’ Export / Import bundle buttons call. Use these directly for manual sharing between sites without going through Cloud at all; use the cloud-* tools above when you want Cloud to store and sync the bundle for you. Full detail on Sandbox.

Permissions

Every tool here requires manage_options. The Cloud-connection tools additionally require an active Cloud connection (EMCP Tools → Connection, Cloud section). The block kind on the export/import tools requires an active Pro license (the block Sandbox store doesn’t exist on free sites, so exporting/importing a block cleanly fails with a pro_required error there rather than a fatal).