Adobe Experience Manager logo

Adobe Experience Manager

Manage your Adobe Experience Manager content

Official docs

About Adobe Experience Manager

Adobe Experience Manager lets users create, edit, search, and publish pages or content fragments by describing the work in natural language. The MCP connector supports content updates, campaign-page searches, and launch scheduling while respecting existing AEM permissions.

Connection details

https://mcp.adobeaemcloud.com/adobe/mcp/aem
Transport
Streamable HTTP
Authentication
OAuth

Setup

claude mcp add adobe-experience-manager --transport http https://mcp.adobeaemcloud.com/adobe/mcp/aem

Frequently asked questions

What is the Adobe Experience Manager remote MCP server?

The Adobe Experience Manager remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.adobeaemcloud.com/adobe/mcp/aem, so AI assistants can connect to it without installing or running anything locally. Adobe Experience Manager lets users create, edit, search, and publish pages or content fragments by describing the work in natural language. The MCP connector supports content updates, campaign-page searches, and launch scheduling while respecting existing AEM permissions.

How do I connect to the Adobe Experience Manager MCP server?

Add the endpoint https://mcp.adobeaemcloud.com/adobe/mcp/aem to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the Adobe Experience Manager MCP server require authentication?

Yes. Adobe Experience Manager uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

Which transport does the Adobe Experience Manager MCP server use?

Adobe Experience Manager exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.

More remote MCP servers