Medusa vs Retailcrm MCP
A side-by-side look at the Medusa and Retailcrm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MedusaE-Commerce · Local subprocess (stdio)Medusa v2 store: orders, customers, products, inventory, sales reports and safe write actions.57GoodAuth: oauth 2.0Verdict: choose Medusa for e-commerce work as a local process; choose Retailcrm MCP for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose 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.
Choose Retailcrm MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_orders, get_order, create_order.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Medusa | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 57/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | MEDUSA_READ_ONLYMEDUSA_RAW_APIMEDUSA_TOOLSETSREPORT_TIMEZONEMEDUSA_CONFIRM_DESTRUCTIVE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 12 | 39 |
| Full listing | View Medusa | View Retailcrm MCP |
Tools & capabilities
Medusa tools 12
get_store_inforegions and currencies, sales channels, stock locations, shipping options and profiles, return and refund reasonslist_ordersorders by full-text, date range, customer or status; full detail by ID or order number (`1042`) with payments, refunds, discount codes and returnslist_customerscustomers (also by group or e-mail), order history, total spentlist_customer_groupscustomer groupslist_productsproducts by status, collection, category or tag; variants, options, prices, images, inventory items (by ID or handle)list_catalogcategories (tree), collections, tags, product typeslist_inventorystock per location, `low_stock_threshold` to find what's running outlist_promotionsdiscount codes with conditions, usage and validity; sale and customer-group price listssales_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 backinventory_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`.
Retailcrm MCP tools 39
list_ordersList orders with filters by status, customer name, number, and created-date range. Returns (summary): pagination + array of {id, number, status, total, customer, phone, itemCount, createdAt}. Use detail:'full' for line items/delivery/payments, raw:true for the untouched payload.get_orderGet a single order by RetailCRM id or externalId. Returns a shaped order; detail:'full' adds items, delivery, payments, comments.create_orderCreate an order with line items and delivery. Link an existing customer via customer_id/customer_external_id, or pass first_name (+phone/email) to create one inline. Returns {success, id, order?}.update_orderUpdate an order (status, customer, delivery, comments). Only the fields you pass are sent. Returns {success}.orders_historyOrder change history incl. status transitions; supports incremental sync via filter_since_id and a date window. Returns {history[], pagination}.list_customersList/search customers by name, email, phone, created-date. Returns (summary): pagination + array of {id, name, email, phone, ordersCount, totalSpent}. detail:'full' adds address/externalId/all phones.get_customerGet a single customer by id or externalId. Returns a shaped customer; detail:'full' adds address and contact details.create_customerCreate a customer with name, contacts, address, optional externalId. Returns {success, id}.update_customerEdit an existing customer (name, email, phones, address) by id or externalId. Only the fields you pass are sent. Returns {success}.merge_customersMerge duplicate customers into a target; merged records are DELETED. Returns {success}.customers_historyCustomer field-change log for growth/churn signals and incremental sync. Returns {history[], pagination}.list_productsList catalog products with filters by name, active, group, price range. Returns pagination + array of {id, name, article, active, url, groups, offers}.- +27 more on 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": {
"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"
}
}
}
}
Retailcrm MCP
{
"mcpServers": {
"retailcrm-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/retailcrm-mcp"
]
}
}
}
Frequently asked questions
Medusa is categorized under E-Commerce and uses a local stdio subprocess. Retailcrm MCP belongs to E-Commerce and uses a local stdio subprocess. Pick Medusa for e-commerce work and Retailcrm MCP 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.
Medusa is listed as free. Auth: oauth 2.0. Retailcrm MCP has no declared pricing — check the project's own site. 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 retailcrm-mcp 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. Retailcrm MCP has 59/100 (Good) with 1 views, 0 installs and 1 GitHub stars.
