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.
12 tools: 3 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Adobe Marketing Agent MCP run looks like inside Luumen.
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.
This connection exposes write actions such as core-context-management-widget, core-feedback-widget, core-plan completion decision, core-provide feedback, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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.
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.
Connect in minutes. Every action scoped, approved, and audited from day one.