Magento (Adobe Commerce)

Magento (Adobe Commerce)

Drive Magento 2 / Adobe Commerce from any AI agent: products, categories, orders, customers, stock and CMS pages and blocks. 21 tools, Bearer admin-token auth, per-store base URL.

7-day free trial · No credit card · EU-hosted

Ask Magento anything

Try a real prompt against Magento (Adobe Commerce) via AnythingMCP — Claude calls the tools, returns the answer. Press Enter on your own message to install on Cloud.

Install Magento on Cloud
Magento (Adobe Commerce) · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

Setup in 2 minutes

  1. 1Start a free trial on cloud.anythingmcp.com.
  2. 2Click Magento (Adobe Commerce) in the connector store. Paste credentials when prompted.
  3. 3Mint an MCP API key and point your AI client at the generated MCP URL.
Install Magento (Adobe Commerce) now

Guides for Magento

Step-by-step setup for the most popular AI clients.

Setting up Magento (Adobe Commerce)

From the connector definition itself: where to find the credentials, what they need to be allowed to do, and which API this adapter talks to.

This connector uses the Magento 2 REST API (devdocs.magento.com).

Setup:

  1. As Magento admin → System → Integrations → Add New Integration.
  2. Name + email, then on the API tab pick scopes: at minimum Catalog (Products + Categories + Stock), Customers, Sales (Orders + Invoices + Shipments).
  3. Activate the integration → grant access. Magento generates an Access Token (this is the long-lived bearer token).
  4. Set:
    • MAGENTO_BASE_URL = your storefront base URL (e.g. https://shop.example.com)
    • MAGENTO_ACCESS_TOKEN = the integration access token
    • Optionally MAGENTO_STORE_VIEW if you want a specific store view (default 'default' or use 'all')

Authentication: Authorization: Bearer ${MAGENTO_ACCESS_TOKEN}.

Path prefix: /rest/{store_view}/V1/.... The adapter uses /rest/default/V1/ as default — if you need to target a different store view, replace baseUrl accordingly or pass ?storeCode= (Magento accepts both).

Search criteria DSL: Magento has a unique multi-key search syntax for list endpoints:

?searchCriteria[filter_groups][0][filters][0][field]=status
&searchCriteria[filter_groups][0][filters][0][value]=1
&searchCriteria[filter_groups][0][filters][0][condition_type]=eq
&searchCriteria[pageSize]=20
&searchCriteria[currentPage]=1

It's verbose but powerful. The adapter exposes the most common filters as flat params and lets you pass arbitrary criteria via searchCriteria_raw for advanced cases.

SKU as primary key: most product endpoints use SKU (not ID) in the URL: /V1/products/{sku}.

Rate limits: not enforced by Magento core — depends on hosting. On 429 back off.

Out of scope here: GraphQL endpoint (separate), Inventory MSI deep features, B2B/Commerce-only features (shared catalogs, company hierarchies), sales rules editing.

CMS pages and blocks always go through the all store code (/rest/all/V1/cmsPage, /rest/all/V1/cmsBlock), Magento's admin scope, so a page written there is not silently moved to one store view. The create and update tools change the live storefront and are installed switched off; there is no delete tool.

Your AI is two clicks away from Magento (Adobe Commerce).

Install the connector, paste your credentials, ask your AI a question. 7-day free trial, no credit card.