Skip to main content
MCP Directory
Storefronts and marketplaces Official SourceMedium integration

Magento MCP server

Checked September 2026.

Adobe's servers for Magento Open Source and Adobe Commerce serve a coding agent, not a store: one searches Commerce documentation and runs and deploys App Builder actions; the other describes storefront drop-in components. A store's catalog, orders, customers, carts, inventory, and promotions are still reached through the REST, GraphQL, and SOAP web APIs.

Magento MCP options

Magento's servers here do not reach your account. Every fact in a row comes from the publisher's own documentation.

Ways to reach Magento data from an assistant
Option Audience Reads or changes Sign-in Setup
Adobe Commerce development MCP servers Adobe Developers Gives a coding agent Adobe Commerce documentation search and App Builder tooling, including tools that run and deploy App Builder runtime actions (aio-app-deploy). Can write No account data See guide Setup guide (opens in a new tab)
dropins MCP server Adobe Developers Serves structured data about Commerce storefront drop-in components (slots, events, containers, APIs, models, design tokens) for storefronts built on the AEM Boilerplate Commerce starter kit. Read only No account data See guide Setup guide (opens in a new tab)
Magento data through SourceMedium's MCP https://mcp.sourcemedium.com/mcp SourceMedium Ours Merchants Reads Magento data from modeled SourceMedium tables, next to your other connected sources, with canonical metric definitions. Read only OAuth sign-in Setup guide

One MCP server per tool still can't answer a cross-channel question.

Each server brings its own sign-in, its own definition of revenue, and data your assistant can't join to the rest.

SourceMedium joins Magento with the rest of your store, ad, subscription, and returns data, keeps one set of maintained definitions, and gives ChatGPT, Claude, and other assistants a single connection to all of it.