Adobe Commerce (Magento) vs Medusa API + MCP

Adobe Commerce (Magento)

Public Swagger files cover 510 REST operations for the cloud service, the GraphQL schema carries cart, checkout and order mutations, and the cloud service authenticates by OAuth 2 through Adobe IMS. No request rate limit or idempotency key was found in the API documentation, Adobe publishes no MCP server for Commerce, and a licence starts with a sales order.

Medusa API + MCP

MIT core you can self-host, with Medusa Cloud running the same APIs and no GMV fee. The official MCP server is docs-only and limited to Cloud accounts.

Adobe Commerce (Magento)

1. Ask which deployment the store is. The cloud service answers at https://<server>.api.commerce.adobe.com/<tenant-id>/ with no /rest prefix, and other stores at https://<host>/rest/<store-view-code>/
2. On the cloud service, request an IMS token with the commerce.accs scope and send the Store header to pick the store view
3. On a 2.4 store, sign requests with all four integration credentials by OAuth 1.0a. A bare integration token is refused unless the merchant has switched that on
4. Add ?fields= to REST calls and set searchCriteria[pageSize]. Stores with input limits on cap a page at 300 items
5. Don't retry placeOrder or a POST blindly. Read the cart or order back first, because no idempotency key was found

Medusa API + MCP

1. Send x-publishable-api-key on every /store call. It decides which sales channels and products the agent sees
2. Ask for only the fields you need with fields. Store routes reject relations nested more than three deep since 2.20.0
3. Read the store's regions before creating a cart, since prices and shipping options depend on region
4. Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set
5. Read the release notes before upgrading a minor version. Breaking changes land there