About Adobe Marketing Agent
Adobe Marketing Agent MCP provides authorized Adobe marketing context, preferences, and agent capabilities through Adobe's hosted MCP service.
Describe what should happen in Adobe Marketing Agent, and when, in plain words. Whenever builds the workflow and runs it on a schedule, on a webhook, or when another app sends an event.
Connection requirements, provider permissions and optional AI usage apply. Read the runtime limits.
Adobe Marketing Agent MCP provides authorized Adobe marketing context, preferences, and agent capabilities through Adobe's hosted MCP service.
Through its MCP server, where the available tools and permissions support the job.
Connect Claude, Cursor or Codex to the Whenever MCP server and your coding agent can build and deploy the Adobe Marketing Agent workflow. It runs on Whenever afterwards, on its schedule or webhook, with the chat closed.
Set up the Whenever MCP serverAdobe Marketing Agent is a way to ask questions of Adobe Experience Platform in plain language, and Whenever reaches it only through Adobe’s hosted MCP service. It is not a record-level API. Behind the connection, Adobe’s Agent Orchestrator routes each question to specialised agents, such as the Audience Agent, the Journey Agent and the Data Insights Agent, which read from Real-Time CDP, Journey Optimizer and Customer Journey Analytics. The tools listed for the connector are mostly about context: setting the sandbox and data view, switching organisation, user preferences and feedback. A scheduled question therefore needs to set its sandbox and data view first, or the answer may come from the wrong environment.
Access depends on what your organisation has licensed. Adobe lists Experience Platform plus at least one of Real-Time CDP, Journey Optimizer or Customer Journey Analytics, entitlement to Agent Orchestrator and its agents, and sign-in through your organisation’s Adobe account. Answers reflect the signed-in Adobe identity’s permissions: the agent inherits that user’s access and does not grant more. Connect with an identity whose data entitlements match the audience of the report, because whatever it can see may end up in the destination you post to.
Each question has a usage cost. Adobe documents that the agent invokes underlying agent jobs that consume AI credits, with published estimates such as 25 credits for audience management or journey management questions and 50 for journey analysis, and notes that actual use varies with the number of steps. An hourly schedule spends credits every hour whether or not anything changed. Ask on the cadence the decision actually needs, often once a week.
Treat answers as generated analysis. They come back as text, tables or visual summaries, and wording and structure can vary between runs. Adobe’s documentation for the Microsoft 365 version describes the agent as returning read-only insights that do not modify customer data, and recommends reviewing generated analyses before using them for decisions. The examples here keep to reading: name the audience, journey, date range and data view precisely so weekly runs are comparable, label the output as agent-generated, and keep a human in charge of any change to audiences or journeys.
Authored starter briefs to configure with your accounts, not preconfigured workflows.
A single, precisely worded question each Monday, posted with its date and environment so readers know what it covers.
An on-demand check started by a webhook, so a planned change is reviewed against live journeys first.
Catches journeys left in test before a weekend, using a journey management question.
Adobe lists Experience Platform with at least one of Real-Time CDP, Journey Optimizer or Customer Journey Analytics, plus entitlement to Agent Orchestrator and its agents. Your Adobe administrator controls access.
Yes. Questions are routed to agent jobs that consume AI credits; Adobe publishes estimates per job type and says actual use depends on the steps executed. Schedule questions only as often as you need them.
Adobe describes the Microsoft 365 version as read-only insights. The examples here only ask questions; review the tools your MCP connection actually exposes before planning any action that changes data.
The signed-in Adobe identity. The agent inherits that user’s permissions and data entitlements in Experience Platform and does not add a separate permission model.
The connector provides tools to set and switch them, and answers depend on that context. Setting them explicitly on each run keeps a scheduled report from silently reading a different environment.
Describe your first workflow in plain words. One stays live for free, no credit card.
No credit card required