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

Medusa MCP server

Checked September 2026.

Medusa's remote server at docs.medusajs.com answers questions from the Medusa documentation and returns step-by-step implementation guides for a module, workflow, or provider integration, or for a migration from Shopify, WooCommerce, or Magento. A store's own products, orders, customers, carts, and inventory live in each merchant's Medusa application and are out of its reach.

Medusa MCP options

Medusa's server here does not reach your account. Every fact in a row comes from the publisher's own documentation.

Ways to reach Medusa data from an assistant
Option Audience Reads or changes Sign-in Setup
Medusa MCP Remote Server https://docs.medusajs.com/mcp Medusa Registered as com.medusajs/medusa-mcp (opens in a new tab) Developers Answers questions from the Medusa documentation and returns step-by-step implementation guides (for example migrating from Shopify, WooCommerce, or Magento). Read only No account data OAuth sign-in Setup guide (opens in a new tab)
Medusa data through SourceMedium's MCP https://mcp.sourcemedium.com/mcp SourceMedium Ours Merchants Reads Medusa 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 Medusa 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.