Adobe Experience Manager

Yes. Adobe's documentation lists publish and unpublish for assets among the connector's content capabilities, and AEM's Sites OpenAPI specification defines a batch publish operation for content fragments that starts an AEM publishing workflow. Publishing moves content from the authoring environment to the delivery tier, which is what visitors see. Treat every write as potentially reaching production.

Far more than five. Three of the tools are named read-api, write-api and delete-api, and a fourth looks up API specifications, so the tool names describe HTTP verbs rather than operations. Eight published AEM OpenAPI specifications alone define 190 operations, of which 97 mutate content and 20 are deletes.

No, and Adobe says so directly. Adobe's setup documentation states the marketplace connector currently has feature parity with the Content MCP Server and exposes a growing subset of the tools available in AEM's MCP servers. The unified endpoint also covers Experience Governance, while Cloud Manager and Cloud Migration must be added as separate servers.

Fourteen, named by product surface rather than by permission level. Adobe's authorization server advertised scopes including aem.sites, aem.assets.author, aem.fragments.management and aem.repository on 2026-08-22. None distinguishes reading from writing or deleting, so consent cannot grant a read-only session at the OAuth layer.

Yes. One of the five listed tools is named delete-api, and AEM's published specifications define twenty delete operations across pages, assets, folders, tags, content fragments, launches and live copies. One of them deletes a content fragment and starts the unpublish process in the same call, so a single request can remove content from a live site.

Through AEM's existing user permissions, not through the connector. Adobe states that MCP tools run under the authenticated user's identity and enforce that user's existing AEM permissions, so an agent can do exactly what its operator can. Organisations wanting narrower limits must email Adobe support to request restrictions per program, environment or environment type.

Adobe advises against it for destructive work. Its documentation states that for scenarios which modify or delete content, practitioners should use the AI Assistant interface rather than invoking MCP tools directly, because the AEM Agents run by AI Assistant include built-in safeguards. That guidance appears in the same article that documents the connector endpoint.

AEM as a Cloud Service, with release 26309 as the floor for asset search. Adobe's documentation names 26309 as the minimum release version for reaching Assets Search through the MCP endpoint, and describes the unified AEM MCP Server as a July 2026 release. The Experience Governance capability additionally requires an agents trial or a paid licence.