Adobe Commerce MCP integration for AI agents.
Connect AI agents to Adobe Commerce through 4 structured actions, including get category, get product, and list categories. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Adobe Commerce integration exposes
The Adobe Commerce Agent App exposes 4 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent retrieve one adobe commerce category by category id, retrieve one adobe commerce product by sku, and retrieve the adobe commerce category tree with optional root and depth limits. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Adobe Commerce account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Adobe Commerce capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_categoryREADRetrieve one Adobe Commerce category by category ID.
INPUTS: categoryId / storeId / fields / storeCode
get_productREADRetrieve one Adobe Commerce product by SKU.
INPUTS: sku / editMode / storeId / forceReload / fields
list_categoriesREADRetrieve the Adobe Commerce category tree with optional root and depth limits.
INPUTS: rootCategoryId / depth / fields / storeCode
list_productsREADList Adobe Commerce products with optional searchCriteria filters and pagination.
INPUTS: filterGroups / sortOrders / pageSize / currentPage / fields
INPUT CONTRACTS
Know what the action needs before it runs.
get_category
categoryIdREQUIRED- The numeric Adobe Commerce category ID.
storeIdOPTIONAL- The numeric store ID to read the category from.
fieldsOPTIONAL- Optional Adobe Commerce fields selector used to return a partial response.
storeCodeOPTIONAL- Optional Adobe Commerce store view code to place between /rest and /V1.
get_product
skuREQUIRED- The Adobe Commerce product SKU.
editModeOPTIONAL- Whether Adobe Commerce should return edit-mode product data.
storeIdOPTIONAL- The numeric store ID to read the product from.
forceReloadOPTIONAL- Whether Adobe Commerce should force a product reload.
fieldsOPTIONAL- Optional Adobe Commerce fields selector used to return a partial response.
list_categories
rootCategoryIdOPTIONAL- Category ID to use as the category tree root.
depthOPTIONAL- Maximum category tree depth to return.
fieldsOPTIONAL- Optional Adobe Commerce fields selector used to return a partial response.
storeCodeOPTIONAL- Optional Adobe Commerce store view code to place between /rest and /V1.
list_products
filterGroupsOPTIONAL- Adobe Commerce searchCriteria filter groups. Groups are ANDed together.
sortOrdersOPTIONAL- Adobe Commerce searchCriteria sort orders.
pageSizeOPTIONAL- Maximum number of products to return.
currentPageOPTIONAL- One-based result page to request.
fieldsOPTIONAL- Optional Adobe Commerce fields selector used to return a partial response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Category
Retrieve one Adobe Commerce category by category ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_categoryVerify with Get Product
Retrieve one Adobe Commerce product by SKU. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_productSAFETY BOUNDARY
Operate Adobe Commerce with explicit limits
- Authorize Adobe Commerce with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Adobe Commerce data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Adobe Commerce rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Adobe Commerce task completed successfully.
CONNECTION MODEL
API key
Adobe Commerce Admin access token sent as an Authorization Bearer token. Learn about Adobe Commerce API authentication at https://developer.adobe.com/commerce/webapi/get-started/authentication/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Adobe Commerce.