Adobe Experience Manager MCP Server

Adobe-hosted MCP servers for Adobe Experience Manager as a Cloud Service. Manage pages, content fragments, assets, workflows, and Cloud Manager via natural language.

Content & CMS by Adobe OAuth2 active

Connect (Remote Server) Docs

Overview

Adobe Experience Manager (AEM) MCP Servers are official, Adobe-hosted Model Context Protocol endpoints that expose AEM as a Cloud Service to AI clients like Claude, ChatGPT, Cursor, VS Code, JetBrains IDEs, GitHub Copilot, Cline, and Microsoft Copilot Studio. They let authors, developers, and operators describe content and platform tasks in plain language and have the AI invoke the appropriate AEM APIs across pages, content fragments, experience fragments, assets, workflows, and Cloud Manager.

Adobe currently publishes several MCP endpoints under https://mcp.adobeaemcloud.com/adobe/mcp/: a /content server with full CRUD on pages, fragments, and assets; a /content-readonly server for safer get/list/search workflows; a /cloudmanager server for managing programs, environments, repositories, and pipelines; an /experience-governance server for brand compliance evaluation; and a /da server for Document Authoring. Documentation references roughly 57 tools across these surfaces, including page CRUD, fragment patching with optimistic concurrency, model discovery, and asset import.

Authentication is handled through Adobe IMS using your Adobe ID, so MCP calls inherit the same AEM permissions a user has in the authoring environment. Because the server is Adobe-hosted, there is nothing to install or self-host: clients add the streamable HTTP MCP URL, complete the Adobe login flow, and the tools become available in the AI client.

Tools

Tool	Description
`get-aem-page-content`	Retrieve the content of an AEM page by path.
`resolve_fragment_path`	Resolve a content fragment to its canonical path in the repository.
`get_fragment`	Fetch a content fragment's data.
`create_fragment`	Create a new content fragment from a model.
`patch_fragment`	Apply a patch to an existing content fragment with optimistic concurrency.
`list_models`	List available content fragment models in the AEM instance.
`get_model`	Fetch the definition of a specific content fragment model.
`Page CRUD tools`	Create, read, update, and delete pages and list sites in AEM as a Cloud Service.
`Asset tools`	Import assets with status tracking and search asset libraries (asset search requires opt-in).
`Cloud Manager tools`	Manage Cloud Manager programs, environments, repositories, and pipelines.
`Experience Governance tools`	Evaluate content against brand compliance rules.

Setup Guide

Prerequisites

An Adobe Experience Manager as a Cloud Service tenant and an Adobe ID with permissions in that environment.
An MCP-capable client: Claude (web or Desktop), ChatGPT, Cursor, VS Code, a JetBrains IDE with GitHub Copilot, Cline, or Microsoft Copilot Studio.

Available Adobe-hosted MCP endpoints

All endpoints are under https://mcp.adobeaemcloud.com/adobe/mcp/:

/content: full CRUD for pages, content fragments, and assets
/content-readonly: read-only get, list, and search
/cloudmanager: Cloud Manager programs, environments, repos, pipelines
/experience-governance: brand compliance evaluation
/da: Document Authoring

Setup in Claude (web)

Open Settings, then Connectors, then "Add custom connector".
Enter a display name like "AEM Content MCP Service" and the URL https://mcp.adobeaemcloud.com/adobe/mcp/content.
Click Connect and complete the Adobe ID login flow.
On the Tool permissions page, set each tool to Always allow, Ask for permission, or Never allow.
In a chat, open the tools menu and enable the connector before prompting.

Setup in Claude Desktop

Add the server to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the Windows equivalent:

{
  "mcpServers": {
    "aem-content": {
      "type": "streamable-http",
      "url": "https://mcp.adobeaemcloud.com/adobe/mcp/content"
    },
    "aem-cloud-manager": {
      "type": "streamable-http",
      "url": "https://mcp.adobeaemcloud.com/adobe/mcp/cloudmanager"
    }
  }
}

Restart Claude Desktop, then sign in with your Adobe ID when prompted. No API key or token configuration is required because Adobe IMS handles auth.

Other clients

Cursor, VS Code, JetBrains, Cline, and Copilot Studio all accept the same streamable HTTP URL through their MCP configuration UIs. See the per-client setup pages under Adobe Experience League, "Using MCP with AEM as a Cloud Service".

Use Cases

Bulk-create or update content fragments from a spec or spreadsheet without writing AEM API code.
Audit a site by listing pages under a path and reporting which use a given template or component.
Patch a localized fragment field across many locales while respecting optimistic concurrency.
Trigger and monitor Cloud Manager pipelines, or inspect environments and repositories, from an IDE chat.
Evaluate draft pages or fragments against brand governance rules before publishing.

Example Prompts

"List all content fragment models under /conf/wknd and show the fields on the Article model."
"Create a new Article content fragment at /content/dam/wknd/en/articles/launch-recap using the Article model, with these field values."
"Find all pages under /content/wknd/us/en that use the hero component and summarize their headlines."
"Patch the ctaLabel field on every Article fragment in /content/dam/wknd/en/articles from 'Learn more' to 'Read article'."
"Show me the latest pipeline executions for Cloud Manager program 12345 and report any failed steps."

Pros

Official and hosted by Adobe, so there is no server to deploy or maintain.
Auth uses Adobe IMS with your Adobe ID, so MCP actions inherit existing AEM permissions and governance.
Broad coverage across pages, content fragments, assets, workflows, and Cloud Manager (around 57 tools).
Works out of the box with Claude, ChatGPT, Cursor, VS Code, JetBrains, GitHub Copilot, Cline, and Copilot Studio.

Limitations

Requires AEM as a Cloud Service. On-prem AEM 6.5 and AMS customers are not covered by the Adobe-hosted servers.
The available tool set evolves over time, and exact tool names and parameters are best discovered at runtime via tools/list rather than from static docs.
Some capabilities such as asset library search require an opt-in request to Adobe.

Alternatives

easingthemes/aem-mcp-server: community open-source MCP server for AEM with content, component, and workflow tools.
indrasishbanerjee/aem-mcp-server and aemaacs-mcp-server: community implementations with read and write servers for AEM as a Cloud Service.
arkadiusz-rosiak/aem-dev-mcp: developer-focused TypeScript MCP server for OSGi bundles, configurations, and health checks.