The DXP Catalyst Update - July 29, 2026

OPENING

Agent connectivity is settling into table stakes, and that's good news for buyers, because it frees up the evaluation to focus on what actually separates platforms. This period Contentful shipped a Remote MCP Server at no charge to all customers, landing in a field where Optimizely, Adobe, Sitecore, Contentstack, and Acquia have all wired in or are wiring in the same agent access. Once every serious vendor offers it, connectivity no longer separates one platform from another, and the more useful question sits one layer down.

It becomes less about whether an agent can reach your content and more about what the agent finds when it gets there. That turns on content modeling depth, workflow governance, and structured taxonomy, the parts of the stack no connectivity announcement can paper over and few demos show.

Sitecore's July 15 launch pointed at that same layer from a different angle, tying AI answer visibility to governed content action. Connectivity gets an agent to the content, but whether the content is modeled and governed well enough to act on is a separate question, and that's the one Sitecore's move is aimed at. Neither release is aimed at the other's problem, but both land in the same place once you follow them through: the value now sits in the content foundation underneath, not the connection into it. The rest of this edition tracks where that shows up across the field.

INDUSTRY PULSE

The MACH Alliance added an Agent Readiness dimension to its free Maturity Assessment, the first formal agentic-readiness measurement from the composable ecosystem's primary standards body. The reason this matters to a buyer is leverage: it gives organizations a vendor-neutral measurement stick for pressing a platform on agentic capability, rather than accepting the vendor's own framing of what "agent-ready" means. Alongside it, the first MACH AI Exchange Hackathon surfaced a finding worth carrying into evaluations, that the strongest agents came from teams who invested in orchestration logic and human-in-the-loop approval rather than interface polish. That maps directly to where the DXP vendors are competing this period, and it tells a buyer which capabilities to weight when comparing agentic roadmaps.

VENDOR ROUNDUP

Acquia

Fair Trade Drupal Initiative Reportedly Expanding to the Global Partner Ecosystem

Acquia's Fair Trade initiative, which directs a share of qualifying partner revenue to the Drupal Association and counts toward Drupal Certified Partner status, is reported to be expanding from its pilot cohort to the broader global partner base. For buyers whose platform strategy depends on the long-term health of the Drupal project, how Acquia funds that foundation is a relevant evaluation input.

Contentful

Remote MCP Server Reaches General Availability at No Charge

Contentful announced on July 21 that its Remote MCP Server has moved from beta to general availability, free to all customers. Any agent supporting the Model Context Protocol can now access and manipulate Contentful content without a custom integration layer. Worth noting for anyone scoping the rollout: the remote server is free, but it does not switch on globally. It requires the Contentful MCP app to be installed and configured per space and environment, where an admin sets which tool categories are exposed and whether each is read-only or read/write. That per-environment gating is a governance feature rather than a catch, and it means "free to all customers" describes the price, not a one-click deployment. In the same period Contentful released Contentful Skills, a free open-source set of agent skills that drops Contentful expertise into Claude Code, Cursor, GitHub Copilot, and more than 30 other coding agents. The pattern is consistent: give away agent access, then compete on what happens once the agent connects.

Contentstack

Partner “Summer School” Series Opens

Contentstack has opened a partner-facing Summer School webinar series walking through its product ecosystem, with the first session this week. It has not produced announcements yet, but it is the kind of channel where product-ecosystem detail tends to surface, and I am expecting news to come out of it over the coming weeks.

Optimizely

Summer ‘26 Roadmap Session Previews a Conversion Data Layer and Native MCP

Optimizely used its Summer '26 roadmap session this period to preview its next wave of Opal capabilities. These are roadmap previews rather than shipped features, and I am tracking them as direction, not availability.

• Adaptive Intelligence, an org-specific model trained on what converts on a customer's own site, positioned to surface underserved audiences and predicted-lift test hypotheses rather than generic suggestions. This is the item I would watch most closely. A proprietary conversion data layer is harder for competitors to match than another agent.

• Limitless 1:1 ABM, agent-built account pages that live on a crawlable URL on the customer's own domain, refresh automatically as CRM signals and news shift, and connect natively to Salesforce.

• Remote MCP support for Opal, connecting to any platform through a remote MCP. This previews the same capability Contentful shipped to GA this period, which reinforces that MCP is becoming a baseline expectation across vendors.

• Analytics moving into the experimentation workflow, with multiple stats engine options and an audit log that labels AI-authored changes distinctly from human-made ones, a governance detail that lines up with the human-approval patterns showing up elsewhere this period.

Separately, Optimizely is holding Opticon in New York on September 1, with agentic-AI breakout sessions and roadmap access on the agenda.

Sitecore

July 15 Launch Connects Scrunch to Governed Content Action through Marketing IQ

Sitecore delivered the launch it pre-announced as its biggest moment since SitecoreAI, and it answers the question I raised when the Scrunch acquisition closed in June: how deeply would Scrunch integrate, and on what timeline. Scrunch is now inside SitecoreAI, showing where a brand is or is not cited in AI-generated answers, tracking prompts, and surfacing the actual exchanges. Its remediation recommendations route into SitecoreAI, either to teams directly or to governed AI agents that follow approval workflows before anything publishes. The headline component is Marketing IQ, an intelligence layer connecting content, brand context, customer data, and performance so agents work from the brand's own standards and from what has converted before. A companion release, Knowledge Studio, brings approved internal knowledge into what those agents draw on.

One element deserves a careful read. Scrunch AXP serves AI crawlers a clean, structured version of a page while humans see the full site and search engines see standard pages. Serving agents a different representation than humans receive is a technique buyers should evaluate on its own terms, including how it sits with search engine guidelines, rather than take at face value. The governed-action model, where AI-generated content passes through approval before publishing, is the part I would weight most heavily.

WHAT I’M WATCHING

Adobe heading into August carries more weight than the market seems to be assigning it. Some background for anyone not tracking the Adobe estate closely: Adobe Experience Manager, its enterprise CMS, has long been deployed by large organizations under Adobe Managed Services, an arrangement where Adobe runs the infrastructure while the customer keeps the more customizable, on-premise-style version of the product. Many enterprises with heavily tailored AEM implementations have run this way for years, because it let them keep deep customization without managing the servers themselves.

Support for AEM 6.5 under Managed Services ends August 31, 2026, and that deadline forces a decision these organizations cannot defer much longer: move to AEM 6.5 LTS or move to AEM as a Cloud Service. The LTS path, long-term support, keeps a customer on the 6.5 line with continued maintenance and security patching but no new feature development, buying time on the current architecture. The Cloud Service path is a re-platform onto Adobe's SaaS offering, with the migration cost and operational change that carries, and for organizations with years of accumulated customization that migration is rarely small.

These are not interchangeable options with a later reconciliation point. One preserves the existing footprint and defers the harder work, the other commits to a multi-year direction now. Organizations that deferred the decision while waiting for clarity may find the August 31 date does not wait with them, and the window to choose deliberately rather than under deadline pressure is closing.

Governance is converging on a shared default across vendors, faster than I expected. Sitecore's launch routes AI-generated content through approval workflows before publishing. The strongest teams in the MACH hackathon built human-in-the-loop approval into their agents. Optimizely's roadmap includes an audit log that separates AI-authored changes from human ones. The operational question none of these roadmaps answers is who inside a buyer organization owns the approval step, and who is accountable when it is skipped, misconfigured, or absent. Buyers who assign that ownership before deploying publishing-capable agents will be in a stronger position than those discovering the gap after something ships without review.

ONE QUESTION WORTH ASKING

Once agent connectivity is free and universal, the differentiator is what an agent can do after it reaches your content. Is your platform selection weighing content modeling depth and workflow governance as heavily as it weighs the connectivity that is about to become table stakes?