Adobe Commerce (Magento) vs Commerce Layer 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.

Commerce Layer API + MCP

Public OpenAPI 3.0 file and llms.txt. No price between the free plan and a sales-quoted Enterprise contract.

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

Commerce Layer API + MCP

1. Call get_resource_schema before any write. Preflight rejects bad filter shapes before they reach the API
2. Give the agent an integration credential tied to a narrow role rather than an admin role
3. On a 429, wait out the sliding window. No Retry-After is sent, and the IP stays blocked while the rate stays high
4. Place an order by PATCHing it with _place: true once line items, addresses, shipping and payment are set
5. Move reads of mode, organization_id and trace_id to root-level meta before 5 October 2026