Adobe unveiled the CX Enterprise Coworker at Adobe Summit 2026 on April 20, positioning it as an agentic orchestration layer for customer experience teams. Per Adobe’s Newsroom announcement, the product enables “agentic-enabled workflows for customer experience orchestration” on top of the Adobe Experience Platform.
The platform context Adobe offers is substantial: the company states that 99% of the Fortune 100 uses Adobe’s AI and that the Experience Platform powers more than 1 trillion global experiences annually. These are platform-level figures, not metrics specific to the CX Enterprise Coworker. They establish the scale at which this orchestration layer would operate if customers adopt it broadly, that’s meaningful context, not a performance claim.
According to coverage of the Adobe Summit 2026 announcement, CX Enterprise Coworker integrates with AWS, Anthropic, Google, and OpenAI via the Model Context Protocol, though these specific integration details were not confirmed in the available Adobe Newsroom source text. If accurate, the MCP angle is the more significant story. Model Context Protocol is a cross-vendor interoperability standard that allows enterprise systems to route tasks to whichever AI model is best suited rather than locking into a single provider’s stack. Adobe integrating with four major AI providers through a shared protocol would be a meaningful signal that enterprise AI is moving toward composable, multi-vendor architectures rather than walled gardens.
The verified story is narrower: Adobe launched a generally available multi-agent orchestration product for CX teams on April 20. The product’s architecture is described as translating high-level business goals, coverage uses an example like “increase cross-sell by 3%”, into automated, multi-step workflows. That framing positions it as a business-intent layer rather than a task automation tool. The distinction matters for buyers: a system that takes a business outcome as input and orchestrates the steps to pursue it is architecturally different from a system that automates a predefined sequence of tasks.
Marketing technology practitioners and CX platform architects are the primary audience for this launch. Enterprise IT teams evaluating agentic AI for business process automation will want to track whether the MCP integration details are confirmed in full documentation. The sourced capability is compelling; the specific partnership architecture needs verification before procurement conversations.
What to watch: Adobe’s full technical documentation post-Summit, which should clarify the integration architecture. Also worth tracking is whether other major marketing technology platforms (Salesforce, HubSpot, SAP) announce comparable MCP-based integrations, if they do, the cross-vendor interoperability pattern The Filter flagged becomes a genuine trend story worth a dedicated deep-dive.