Several guides circulating online describe a specific Composer package, exact Magento version requirements, and an admin panel toggle for UCP on Adobe Commerce. We could not verify any of these claims against Adobe's own documentation or announcements, and the level of specificity in those guides (exact package names, precise version numbers) matches a pattern of AI-generated SEO content rather than real documentation. This guide sticks to what Adobe has actually confirmed itself.
What Adobe has actually committed to
Per Adobe's own blog, Adobe Commerce is committed to supporting both the Universal Commerce Protocol (UCP) and the Agentic Commerce Protocol (ACP), building on an earlier commitment to Google's Agent Payments Protocol (AP2). Adobe frames this as helping brands "gain visibility across AI-driven shopping channels while maintaining full control over customer relationships, branding, and commerce data." This is a real, named commitment to the same open standards Shopify and WooCommerce plugin developers are building against, not a proprietary alternative.
What has actually shipped: the Commerce MCP Server
At Adobe Commerce Summit 2026, Adobe introduced the Commerce MCP Server, which gives developers programmatic access to catalog, cart, pricing, inventory, promotions, checkout, order management, and post-purchase data through the Model Context Protocol. This is real, available developer infrastructure, but it is worth being precise about what it actually is.
Per analysis from an Adobe implementation partner who has used it on a live client project, the Commerce MCP Server is "an accelerator for building ACCS extensions and integrations, not a customer-facing feature." It is tightly coupled with Adobe's Commerce Integration Starter Kit and intended for developers building custom AppBuilder integrations, not something that automatically produces a live, agent-facing UCP manifest on its own. A merchant does not get discoverable to AI shopping agents simply by having Commerce MCP Server available, a developer still has to build the integration.
What this means in practice
For a merchant on Adobe Commerce today, getting a working /.well-known/ucp manifest live means custom development, similar in spirit to a merchant on a headless or custom stack rather than a Shopify-style toggle. The Commerce MCP Server and Commerce Integration Starter Kit narrow the amount of custom plumbing a developer needs to write, but they are accelerators for that developer, not a feature a store owner can enable themselves.
Adobe has also announced partnerships with PayPal, Stripe, and Adyen specifically around checkout standards for AI and marketplace contexts, layered on top of the UCP and ACP commitment. These payment-side partnerships mean the payment layer of an eventual Adobe Commerce UCP implementation has real infrastructure behind it, even though the discovery and manifest layer still requires custom work today.
Verify before you build
Given how much unverifiable, specific-sounding guidance is circulating for Magento and UCP, the most reliable path is to check the actual current state of Adobe's developer documentation yourself before starting any implementation work, since this is an area that is genuinely moving. Once you do build a manifest, or if you want to check whether your current setup already has one, our checker will tell you directly rather than relying on secondhand claims.
Check what your store actually publishes
Whatever your Adobe Commerce setup, check directly whether it publishes a valid UCP manifest.
Frequently asked questions
No. Shopify offers a built-in toggle for UCP-compatible Agentic storefronts. Adobe Commerce has committed to supporting UCP and ACP as standards and has shipped developer infrastructure (the Commerce MCP Server) toward that goal, but there is no turnkey, merchant-facing toggle that automatically publishes a UCP manifest.
A developer tool Adobe introduced at Commerce Summit 2026 that gives developers programmatic access to catalog, cart, pricing, inventory, and other commerce data through the Model Context Protocol. Per an Adobe implementation partner, it is an accelerator for building custom integrations, not a customer-facing feature that produces a live UCP manifest on its own.
We could not verify claims circulating online about specific Composer packages or plugins for Magento UCP support against any primary Adobe source. Treat highly specific guides (exact version numbers, exact package names) with skepticism unless you can verify them against Adobe's own current developer documentation directly.
Yes, per the same Adobe announcement covering UCP. Adobe has committed to both standards, alongside an earlier commitment to Google's Agent Payments Protocol (AP2).