Adobe Experience Manager

Create, edit, publish and delete AEM pages, content fragments and assets from an agent.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Adobe Experience Manager connector does

The Adobe Experience Manager MCP server connects an AEM as a Cloud Service authoring environment to Claude, ChatGPT and any MCP-compatible agent. Anthropic lists five tools that create, read, update, delete and publish pages, content fragments and assets. Because AEM runs live websites, these writes can reach production. Sign-in is OAuth with an Adobe ID.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Adobe Experience Manager tools (5)

  • list-aem-environments
  • lookup-api-spec
  • read-api
  • write-api
  • delete-api

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The tool count is not an operation count. Three of the five names are HTTP verb dispatchers. Counting them as five capabilities understates the surface by roughly forty times on the eight specifications we measured, and by more across the full catalogue.
  • Neither enumeration confirms the other. Anthropic's five names appear nowhere in Adobe's documentation, and Adobe's seven documented tool names appear nowhere in the directory listing. We could not find a first-party enumeration of the marketplace connector's tools, so the five are unverified against the vendor in either direction.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no readOnlyHint or destructiveHint is reported here, and no parameter-level detail. The operation counts come from Adobe's published OpenAPI specifications, not from the server.
  • No OAuth scope separates reading from writing. All 14 advertised scopes name product surfaces. The resource descriptor declares no scopes_supported at all. A read-only session cannot be expressed at consent.
  • Read-only mode exists but is not self-service. Adobe grants it by request to aemcs-mcp-feedback@adobe.com, optionally per program, environment or environment type. Until you ask, the content category is read-write by default.
  • Tool names are explicitly unstable. Adobe instructs integrators not to hardcode them and to handle notifications/tools/list_changed, so any allowlist built on the five names will drift.
  • Cloud Manager and Cloud Migration are not included. Their capabilities — including running deployment pipelines — require adding those servers separately.
  • Experience Governance is licence-gated. It needs an agents trial or a paid licence.
  • Adobe documents an accuracy caveat. Its guidance says LLMs are "prone to occasional errors", that the same prompt may yield different results, and that outputs should always be reviewed before being applied to production content.
  • Whether publishing notifies anyone is unresolved. We found no Adobe documentation stating whether a publish through MCP triggers approval workflows or notifications in a site with editorial review configured, and we did not test it. Treat it as unknown.

Frequently asked questions

Can the Adobe Experience Manager connector publish content to a live website?

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.

How many operations can the five AEM MCP tools actually reach?

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.

Does the Claude connector expose every AEM MCP tool?

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.

What OAuth scopes does the AEM MCP server request?

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.

Can an AI agent delete AEM pages or assets?

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.

How does AEM limit what the MCP connector can do?

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.

Should I use MCP tools directly for AEM content changes?

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.

Which AEM version is required for the MCP connector?

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.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

  • Agility CMS

    Model content, author pages and publish to a live site from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Adobe Experience Manager to work.

Connect Adobe Experience Manager once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio