Adobe Experience Manager MCP modules

The Adobe Experience Manager MCP connector is a dedicated Fusion integration for Adobe Experience Manager’s own Model Context Protocol (MCP) server. Unlike a typical connector, where each module performs one fixed action, this connector has a single module that accepts an open-ended, plain-English instruction and lets an AI model decide which Adobe Experience Manager operations are needed to fulfill it, across areas like sites, digital assets, content fragments, folders, the content repository, and content AI.

This connector is dedicated to Adobe Experience Manager’s own MCP server. It does not support other, unrelated MCP servers. For a connector you can point at any MCP server instead, use the MCP Agent connector.

For information on the MCP Agent connector, see MCP Agent module.

NOTE
Responses from this module are AI-generated and can occasionally be imperfect, even with every available safeguard in place. This module is appropriate for automation where a human isn’t reviewing every run in real time, but it isn’t a guarantee of the deterministic behavior you’d get from a traditional Adobe Experience Manager module.

Access requirements

Expand to view access requirements for the functionality in this article.
table 0-row-2 1-row-2 2-row-2 3-row-2 layout-auto html-authored no-header
Adobe Workfront package

Any Adobe Workfront Workflow package and any Adobe Workfront Automation and Integration package

Workfront Ultimate

Workfront Prime and Select packages, with an additional purchase of Workfront Fusion.

Adobe Workfront licenses

Standard

Work or higher

Adobe Workfront Fusion license

Operation-based: Available to organizations with operation-based licenses

Connector-based (legacy): Workfront Fusion for Work Automation and Integration

Product If your organization has a Select or Prime Workfront package that does not include Workfront Automation and Integration, your organization must purchase Adobe Workfront Fusion.

For more detail about the information in this table, see Access requirements in documentation.

For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.

Prerequisites

  • You must have an Adobe Experience Manager account to use this module.

Connect Adobe Experience Manager MCP to Workfront Fusion connect-adobe-experience-manager-mcp-to-workfront-fusion

The Adobe Experience Manager MCP connector uses OAuth to connect to Adobe Experience Manager. There are no connection fields to fill in manually, such as a username, password, or API key.

To create a connection:

  1. In the Adobe Experience Manager MCP module, click Add next to the Connection field.

  2. Select whether you are connecting to a Production or Non-production environment.

  3. Select whether you are connecting to a Service account or a Personal account

  4. Click Continue.

    You are redirected to Adobe’s login page.

  5. On the Adobe login page, Log in and approve access.

You are redirected back to Workfront Fusion, and the new connection is available in the module.

Adobe Experience Manager MCP module and its fields

Currently, there is only one module in the Adobe Experience Manager MCP connector.

Process a user prompt

This action module sends a plain-English instruction to Adobe Experience Manager’s MCP server and returns the AI’s answer.

Each run of this module is a single, self-contained execution, similar to sending an email rather than having a live conversation. The AI cannot ask a follow-up question and wait for your reply. Instead, it makes its best judgment and returns a complete answer. If your prompt is ambiguous, the AI states any assumption it made as part of its answer, rather than stopping to ask you to clarify.

IMPORTANT
This module only takes a write or delete action when your prompt actually asks for one. It doesn’t take any extra actions you didn’t request, even in the same run where it’s carrying out something else you did ask for.

Because each run is independent, the module has no memory of previous runs by itself. To create a multi-turn, conversational experience across several runs, store the previous question and answer. You can use a Data Store for this, and then include that history as text at the start of your next prompt, followed by the new question.

For information on Data Stores, see Data Store.

LLM key (Optional, advanced)

By default, this module processes your prompt using Adobe's own AI service, and you do not need to select a key.

To use your own AI provider instead, select an existing LLM key, or create a new one by clicking Add and entering the following information:

  • Key name: Enter a name for the new key.
  • LLM: Select the large language model that this key is associated with. Supported providers are OpenAI, Anthropic Claude, and Amazon Bedrock.
  • Key: Enter or map your API key for the selected provider.
  • Model: Select the LLM model that the key will use.
  • Other fields: Enter values for any other fields that your LLM requires.
Connection
For instructions about connecting your Adobe Experience Manager account to Workfront Fusion, see Connect Adobe Experience Manager MCP to Workfront Fusion in this article.
User Prompt

Enter or map the instruction, in plain English, that you want the AI to carry out.

Example: Find all assets in the marketing folder that haven't been updated in 90 days.

Read-only tools (Optional)

Restrict which read-only Adobe Experience Manager actions the AI is allowed to call — actions that only look something up, such as finding an asset or reading a page's content, and never change anything.

If you leave this field empty, all read-only actions are allowed.

Write/delete tools (Optional)

Restrict which write or delete Adobe Experience Manager actions the AI is allowed to call — actions that change something, such as updating a page, publishing content, or deleting an asset.

If you leave this field empty, all write and delete actions are allowed. To guarantee that an unattended scenario never takes a destructive action, we recommend leaving this field set to a deliberately empty selection rather than leaving it unrestricted.

The module returns the AI’s final answer, as text, along with a record of what happened while producing that answer, including which tools were called, whether each call succeeded, and how long processing took.

recommendation-more-help
workfront-fusion-help-workfront-fusion