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

Elastic Path API + MCP

Cart, promotion code, checkout and order endpoints cover the whole test flow. MCP server exposes 95 tools with full CRUD, no read-only mode and no public source or licence.

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

Elastic Path API + MCP

1. Use a client_credentials token server-side only. It has full CRUD on the store
2. Pick the base URL for the store's region (useast or euwest), or every call returns 401
3. Loading the MCP server costs 95 tool definitions, so enable it only for agents that need the back office
4. On a 429, wait a few seconds and retry. No Retry-After header is sent
5. Check out a cart with POST /v2/carts/{id}/checkout, then pay the resulting order