Medusa vs Sample Shop MCP server

A side-by-side look at the Medusa and Sample Shop MCP server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MedusaE-Commerce · Local subprocess (stdio)Medusa v2 store: orders, customers, products, inventory, sales reports and safe write actions.57GoodAuth: oauth 2.0

Sample Shop MCP serverE-CommerceSample shop MCP server: paginated search, idempotent orders, guarded cancellation. Four languages.33EmergingAuth: not declared

Verdict: choose Medusa for e-commerce work as a local process; choose Sample Shop MCP server for e-commerce. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

M
Choose Medusa when

You need dedicated capabilities in the E-Commerce domain.
You prefer a local stdio subprocess transport.
Its auth model fits you: OAuth 2.0.
You have the keys it needs: MEDUSA_READ_ONLY, MEDUSA_RAW_API, MEDUSA_TOOLSETS, REPORT_TIMEZONE, MEDUSA_CONFIRM_DESTRUCTIVE.
You want tools like get_store_info, list_orders, list_customers.

Explore Medusa

S
Choose Sample Shop MCP server when

You need dedicated capabilities in the E-Commerce domain.
You have the keys it needs: UPSTREAM_URL, UPSTREAM_API_KEY.

Explore Sample Shop MCP server

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	M Medusa	S Sample Shop MCP server
Category	E-Commerce	E-Commerce
Quality signal	57/100 · Good	33/100 · Emerging
Install command	Confirmed	Not confirmed yet
Transport	Local subprocess (stdio)	—
Auth	OAuth 2.0	Not declared
Pricing	Free	Free
Required env vars	`MEDUSA_READ_ONLYMEDUSA_RAW_APIMEDUSA_TOOLSETSREPORT_TIMEZONEMEDUSA_CONFIRM_DESTRUCTIVE`	`UPSTREAM_URLUPSTREAM_API_KEY`
Verified owner	Community listing	Community listing
GitHub stars	0	0
Directory activity	0 views 0 installs 0 upvotes	0 views 0 installs 0 upvotes
Tools	12	Not listed
Full listing	View Medusa	View Sample Shop MCP server

Tools & capabilities

Medusa tools 12

get_store_inforegions and currencies, sales channels, stock locations, shipping options and profiles, return and refund reasons
list_ordersorders by full-text, date range, customer or status; full detail by ID or order number (`1042`) with payments, refunds, discount codes and returns
list_customerscustomers (also by group or e-mail), order history, total spent
list_customer_groupscustomer groups
list_productsproducts by status, collection, category or tag; variants, options, prices, images, inventory items (by ID or handle)
list_catalogcategories (tree), collections, tags, product types
list_inventorystock per location, `low_stock_threshold` to find what's running out
list_promotionsdiscount codes with conditions, usage and validity; sale and customer-group price lists
sales_reportrevenue, net revenue after refunds, AOV, units, customers – **compared with the previous period or last year**, day/week/month series, top products and variants, countries, discount codes, sales channels · *interactive dashboard*
customer_reportnew vs returning customers, repeat purchase rate, top customers, lapsed customers worth winning back
inventory_forecastsales velocity vs stock: days of cover, out-of-stock / reorder-now / reorder-soon, suggested order quantities, slow movers · *interactive restock planner*
medusa_requestany Admin API endpoint (`GET`, `POST`, `DELETE` under `/admin/`) for things without a dedicated tool – reservations, exchanges, tax rates… Read-only mode allows `GET` only; writes to `api-keys`, `users` and `invites` are always blocked. Turn it off with `MEDUSA_RAW_API=false`.

Sample Shop MCP server tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Medusa

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "medusa": {
      "command": "npx",
      "args": [
        "-y",
        "medusa-mcp"
      ],
      "env": {
        "MEDUSA_READ_ONLY": "YOUR_MEDUSA_READ_ONLY_HERE",
        "MEDUSA_RAW_API": "YOUR_MEDUSA_RAW_API_HERE",
        "MEDUSA_TOOLSETS": "YOUR_MEDUSA_TOOLSETS_HERE",
        "REPORT_TIMEZONE": "YOUR_REPORT_TIMEZONE_HERE",
        "MEDUSA_CONFIRM_DESTRUCTIVE": "YOUR_MEDUSA_CONFIRM_DESTRUCTIVE_HERE"
      }
    }
  }
}

Sample Shop MCP server

No confirmed install command for Sample Shop MCP server yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Medusa is categorized under E-Commerce and uses a local stdio subprocess. Sample Shop MCP server belongs to E-Commerce and uses an install path we have not confirmed yet. Pick Medusa for e-commerce work and Sample Shop MCP server for e-commerce.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Sample Shop MCP server has no confirmed install command yet — follow its own setup instructions.

Medusa is listed as free. Auth: oauth 2.0. Sample Shop MCP server is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add medusa and sample-shop-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Medusa has a quality signal of 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Sample Shop MCP server has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.