Adobe Marketing Agent MCP
for LuumenAI

Adobe Experience Platform context, sandbox switches, and async task status

Connect Adobe Marketing Agent MCP and Luumen can read your authorized Adobe marketing context from Adobe's hosted MCP service: the current sandbox and dataview, saved preferences, and the status of async tasks running in a conversation. Changes to that context — switching sandbox, dataview, or organization — are previewed and approved before they run. Luumen authenticates with OAuth using dynamic client registration.

Book a DemoDownload Luumen

The Adobe Marketing Agent MCP toolbox

12 tools: 3 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadAdobe-marketing-agent-mcp-widgetThis MCP server offers a comprehensive suite of capabilities designed to enhance user experience with Adobe Experience Platform and related applications.
  • ReadCore-get taskGet task status and events for an async task.
  • ReadCore-list tasksList async tasks for a conversation context_id.
  • WriteCore-context-management-widgetInteractive widget to view and manage user context. Approval by default
  • WriteCore-feedback-widgetCall this widget when the user wants to provide feedback or rate their experience. Approval by default
  • WriteCore-plan completion decisionSubmit the user's final decision to complete or cancel a pending plan. Approval by default
  • WriteCore-provide feedbackSubmit user feedback about their experience with the AI assistant. Approval by default
  • WriteCore-set dataviewSet the current dataview context. Approval by default
  • WriteCore-set sandboxSet the current sandbox context. Approval by default
  • WriteCore-switch orgSwitch to a different organization by exchanging the current token. Approval by default
  • WriteCore-switch sandbox dataviewThis core system tool updates the current sandbox and/or dataview context for the session. Approval by default
  • WriteCore-user preferencesRead or clear the current user's persisted preferences (sandbox, dataview, org, region). Approval by default

One prompt, start to finish

What a governed Adobe Marketing Agent MCP run looks like inside Luumen.

Questions

How does LuumenAI connect to Adobe Marketing Agent MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Adobe Marketing Agent MCP on its own?

Read actions answer immediately. Anything that writes — core-context-management-widget, core-feedback-widget, core-plan completion decision, core-provide feedback, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Adobe Marketing Agent MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
AffindaRead parsed documents, collections, and annotations — change them with approvalAgent MailGive the agent its own mailbox for reading threads and sending updatesAI/ML APIInspect assistants, threads, and runs — and change them as approved stepsAirOps MCPRead AirOps brand context and AEO data, then change prompts as approved steps

Put Adobe Marketing Agent MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen