Spots

Adobe Commerce Added an MCP Layer: Your Catalog Is Now an Agent's Tool

On Thursday, April 9, 2026, an AI shopping agent could call search_shop_catalog on any Shopify store's Storefront MCP endpoint and get products back. On Friday morning, April 10, the same call returned Tool not found: search_shop_catalog. Shopify had moved its catalog tools to the Universal Commerce Protocol shape, renamed the tool to search_catalog, and wrapped its arguments in a new nested catalog object. Developers found out when their agents stopped working and started asking about it on the community forum.

Hold that story, because it's the most useful

Hold that story, because it's the most useful thing you can know before Adobe's version reaches your store. At Summit 2026 in April, Adobe announced a Commerce MCP server that exposes catalog, cart, pricing, inventory, promotions, checkout, order management and post-purchase flows to AI agents. The announcement treats it as a distribution channel: ChatGPT, Gemini, your own shopping assistant, all reading your catalog in real time.

That's true, but the more important change is

That's true, but the more important change is architectural. Your catalog used to be data that your own frontend rendered. Now it's a tool: a named, schema'd function that a language model you don't control decides when to call, with arguments it makes up, and whose output it reads as instructions-adjacent text. That shift has consequences that don't show up in the keynote slides.

Note Status check before we go further. As

Note Status check before we go further. As of this writing, Adobe's own Experience League page for "Commerce MCP for Adobe Commerce" is labelled "Coming Soon" with the note "This feature is coming soon and is subject to change," while some Adobe partners describe it as already running on client projects. Either way, the page doesn't say which deployments get it. Adobe's agentic push is built around Adobe Commerce as a Cloud Service (ACCS) and its SaaS catalog services, so if you're on PaaS or on-prem Magento, don't plan on it arriving for free. The "build your own" section below is your path.

Note Status check before we go further. As

Note Status check before we go further. As of this writing, Adobe's own Experience League page for "Commerce MCP for Adobe Commerce" is labelled "Coming Soon" with the note "This feature is coming soon and is subject to change," while some Adobe partners describe it as already running on client projects. Either way, the page doesn't say which deployments get it. Adobe's agentic push is built around Adobe Commerce as a Cloud Service (ACCS) and its SaaS catalog services, so if you're on PaaS or on-prem Magento, don't plan on it arriving for free. The "build your own" section below is your path. What Adobe actually announced (and what it didn't)

Strip out the marketing and there are three

Strip out the marketing and there are three separate things under the "agentic" umbrella. They get conflated constantly, so it's worth pulling them apart.

The Commerce MCP server. This is the runtime

The Commerce MCP server. This is the runtime piece: an MCP endpoint in front of your live store data. Adobe's developer blog describes it as standardizing how "product data, business rules, and transactional context are presented to LLMs," supporting "cart creation, checkout initiation, payment orchestration, inventory validation, promotions, and returns." That's the piece this article is about.

The developer MCP servers. Completely different thing. aio

The developer MCP servers. Completely different thing. aio commerce extensibility tools-setup installs Adobe's Commerce App Builder MCP server into your coding agent, plus a drop-ins MCP server if you pick the AEM Boilerplate Commerce starter kit. Those touch documentation and code, not store data. They help you write extensions. They don't let a shopper's agent buy anything. If a vendor pitch blurs these two, ask which one they mean.

Protocol support for ACP and UCP. In February

Protocol support for ACP and UCP. In February 2026 Adobe committed to supporting the Agentic Commerce Protocol and the Universal Commerce Protocol, on top of its earlier commitment to the Agent Payments Protocol. Adobe didn't publish a detailed rollout schedule, just "additional capabilities throughout 2026."

What Adobe hasn't published yet, at least not

What Adobe hasn't published yet, at least not publicly, is the part an engineer actually needs: the exact tool names, their input and output schemas, the auth model, rate limits, and how fresh the data behind each tool is. The architecture blog post stays at the level of concepts, with no numbers. So everything below is about the shape of the problem, which doesn't depend on Adobe's final tool list. MCP, ACP, UCP: three layers, not three competitors The alphabet soup gets presented as a standards war. It mostly isn't one. The three protocols sit at different layers.

News

Adobe Commerce Added an MCP Layer: Your Catalog Is Now an Agent's Tool

On Thursday, April 9, 2026, an AI shopping agent could call search_shop_catalog on any Shopify store's Storefront MCP endpoint and get products back.

@spots #dev
Source: Dev.to
See more like this