Adobe Experience Manager MCP server
An AI agent connected to Adobe Experience Manager can manage digital content—creating and publishing pages, uploading and organizing assets in the DAM (Digital Asset Management), setting up multi-site experiences, and automating workflow approvals. Content teams, digital marketers, and web operations professionals use this integration to streamline content deployment and reduce manual content management overhead.
Setting up an MCP server
This article covers the standard steps for creating an MCP server in AI Gateway and connecting it to an AI client. The steps are the same for every integration — application-specific details (API credentials, OAuth endpoints, and scopes) are covered in the Authentication section on this page.
Before you begin
You'll need:
- Access to AI Gateway with permission to create MCP servers.
- API credentials for the application you're connecting (see the Authentication section on this page for what to collect).
Create an MCP server
Find the app in the catalog
- Sign in to AI Gateway and select App Catalog from the left navigation.
- Search for the application you want to connect, then select it from the catalog.
- Select Create MCP Server to start the wizard.
App Configuration
Confirm the Base URL for the API, then, under Tools, select the endpoints you want to expose. Select Next.
MCP Server Setup
- Enter a Name for your server — something descriptive that identifies both the application and its purpose.
- Enter a Description so your team knows what the server is for.
- Set the log level: choose Production Mode for terser logs, or Non-Production Mode for more verbose logs that can help with debugging.
- Select Next.
Authentication
Enter the authentication details for the application. This varies by service — see the Authentication section on this page for the specific credentials, OAuth URLs, and scopes to use.
Review
Look over the summary of your MCP server configuration, then select Create & Deploy. AI Gateway provisions the server and provides a server URL you'll use when configuring your AI client.
Connect to an AI client
Once your server is deployed, you'll need to add it to the AI client your team uses. Select your client for setup instructions:
Tips
- You can create multiple MCP servers for the same application — for example, a read-only server for reporting agents and a read-write server for automation workflows.
- If you're unsure which OAuth scopes to request, start with the minimum read-only set and add write scopes only when needed. Most application pages include scope recommendations.
Authentication
Adobe Experience Manager uses OAuth 2.0 through the Adobe Developer Console and IMS (Identity Management System). Create an OAuth credential in Developer Console linked to your AEM instance, and configure an IMS configuration in AEM Admin to establish the trust relationship. In Adobe Developer Console, go to console.adobe.io, create a new project, and add the AEM API to generate your OAuth credentials.
| Value | Setting |
|---|---|
| Auth endpoint | https://ims-na1.adobelogin.com/ims/authorize/v2 |
| Token endpoint | https://ims-na1.adobelogin.com/ims/token/v3 |
Available tools
The MCP server provides page management, digital asset operations, site configuration, content fragments, and publishing capabilities for complete content management.
Pages & content
| Tool | Description |
|---|---|
| createPage | Create new page from template with specified parent |
| updatePageContent | Modify page title, body, and component properties |
| publishPage | Publish page to live environment |
| unpublishPage | Remove page from live (archive or revert to draft) |
| deletePage | Remove page and child pages from author |
| listPages | Get pages in a path with status and metadata |
Digital assets
| Tool | Description |
|---|---|
| uploadAsset | Upload image, video, or document to DAM |
| getAsset | Retrieve asset metadata and download links |
| updateAssetMetadata | Modify asset title, description, tags, keywords |
| deleteAsset | Remove asset from DAM |
| createAssetFolder | Create folder in DAM hierarchy |
| searchAssets | Find assets by keyword, tag, or metadata |
Sites & structure
| Tool | Description |
|---|---|
| createSite | Set up new site with blueprint or template |
| createLanguageCopy | Generate site translated to different language |
| updateNavigation | Modify site menu structure and links |
| createRedirect | Set up URL redirect for moved or retired pages |
| getPageHierarchy | Retrieve page tree and parent-child relationships |
Content fragments & experience
| Tool | Description |
|---|---|
| createContentFragment | Create structured content block reusable across pages |
| updateContentFragment | Modify fragment body and metadata |
| linkFragmentToPage | Associate content fragment with page |
| createExperienceFragment | Build reusable experience block with components |
| targetFragmentToAudience | Assign fragment visibility to specific audience |
Publishing & workflow
| Tool | Description |
|---|---|
| createPublishingWorkflow | Set up content review and approval process |
| submitForApproval | Route page for reviewer approval before publish |
| getWorkflowStatus | Check approval status and pending reviewers |
| bulkPublish | Publish multiple pages in scheduled operation |
| schedulePublish | Queue page publish for specific date/time |
Tips
Use content fragments for reusable content blocks (e.g., product descriptions, legal disclaimers) so updates propagate across all pages that reference them.
Create language copies for multi-region sites at the site blueprint level to maintain consistent structure while allowing regional customization.
Schedule bulk publish operations during low-traffic periods to minimize performance impact on the author instance during processing.
Tag and organize digital assets with consistent metadata so search and filtering work reliably across your organization.
Set up publish workflows to enforce approval gates for production content, ensuring brand consistency and reducing errors.
Cequence AI Gateway