# Adobe Commerce MCP connector

The Adobe Commerce connector brings attribute sets, base prices, bundle products and carts into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can read and update them as whoever signed in, with every call logged.

Source: https://elaichi.ai/connectors/magento/

## Facts

| | |
| --- | --- |
| Application | Adobe Commerce |
| Category | Ecommerce |
| AI tools | 215 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Adobe Commerce is connected

- Show me the attribute sets that have no attributes assigned
- Which bundle options does the starter kit bundle have?
- Pull up cart 48213 and list what is in it

## Connect Adobe Commerce in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Adobe Commerce.
2. Optionally set Share with, then press Connect.
3. Paste an Adobe Commerce API key. One person generates a token in Adobe Commerce and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Adobe Commerce tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Adobe Commerce MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Adobe Commerce MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Adobe Commerce MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Adobe Commerce MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Adobe Commerce MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Adobe Commerce to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Adobe Commerce tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Adobe Commerce through Elaichi

### Set up a new product line's attributes

Merchandising. Create an attribute set for a new range, add the groups and attributes it needs, and have it ready before the first product is entered.

### Push base prices across a range

Pricing. Search the current base prices for a set of SKUs, then set new ones in one pass instead of opening each product in the Adobe Commerce admin.

### Build a bundle without the admin

Ecommerce. Add options and child products to a bundle, adjust them, and remove the ones that are out of stock, all from a chat window.

### Look up a shopper's cart mid-chat

Support. Pull a cart by its ID to see what a customer has in it before answering a question about a missing item or an unexpected total.

### Audit attribute sets before a cleanup

Operations. List every attribute set and its groups, spot the duplicates and the empty ones, and delete what nobody uses.

### Check a bundle before the campaign goes out

Marketing. List the options and children of a bundle to confirm the landing page matches what Adobe Commerce will actually sell.

## Elaichi vs Zapier MCP vs Composio for Adobe Commerce

All three can connect Adobe Commerce to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Adobe Commerce tools | Allow or restrict single Adobe Commerce tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Adobe Commerce call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Adobe Commerce to Claude?

Connect Adobe Commerce in Elaichi by pasting your Adobe Commerce API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Adobe Commerce is available in Claude.

### Does Adobe Commerce work with ChatGPT and Cursor as well as Claude?

Yes. Once Adobe Commerce is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Adobe Commerce once and every client gets it.

### What can an AI agent actually do with my Adobe Commerce data?

An agent can list and create attribute sets, add attributes and groups to them, search and set base prices, build and edit bundle products and their options, and pull up a cart to see what a shopper has in it. In practice that means asking for the price of a SKU, the contents of cart 48213, or a new attribute set for a product line. Short, concrete asks about Adobe Commerce work better than long sentences.

### Does connecting Adobe Commerce give the AI access to my whole store?

No. Every call to Adobe Commerce runs as the person who signed in, with the access their Adobe Commerce API key already has. Elaichi can narrow that further with roles and restrictions, and it can never widen it.

### Can my team share one Adobe Commerce connection?

Yes. One person connects Adobe Commerce in Elaichi and shares it with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every price change or cart lookup.

### Can I stop an agent from deleting or changing things in Adobe Commerce?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting attribute sets or changing base prices in Adobe Commerce for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Adobe Commerce connection when someone leaves?

Offboarding a person in Elaichi ends their access to Adobe Commerce at once, in every client they used. A shared Adobe Commerce connection keeps working for everyone else on the team. If you disconnect Adobe Commerce in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the Adobe Commerce MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Adobe Commerce is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Adobe Commerce?

Yes. Both let Claude, ChatGPT or Cursor use Adobe Commerce. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Adobe Commerce call.

### How is Elaichi different from Composio for Adobe Commerce?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Adobe Commerce: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 215 Adobe Commerce tools

Every tool below is callable through https://api.elaichi.ai/mcp once Adobe Commerce is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Adobe Commerce attribute set attribute** (Create). Assign an attribute to an attribute set and group.
- **List all Adobe Commerce attribute set attributes** (List). Retrieve related attributes based on given attribute set ID.
- **Delete a Adobe Commerce attribute set attribute by ID** (Delete). Remove attribute from attribute set. `id` is the attribute code to remove from the set. Magento refuses (attribute locked) while a configurable product uses the attribute.
- **Create a Adobe Commerce attribute set group** (Create). Save attribute group. Send the body wrapped as `{"group": {...}}`.
- **List all Adobe Commerce attribute set groups** (List). List attribute set groups. Magento requires a filter on `attribute_set_id` (filter_field=attribute_set_id, filter_value=&lt;set id&gt;); calls without it are rejected. Sort with sort_field and sort_direction. The connector pages automatically (`limit`, default 100, max 300). Raw searchCriteria[filter_groups][N] params also work (see the readme).

- **Delete a Adobe Commerce attribute set group by ID** (Delete). Remove attribute group by id. `id` is the Magento `groupId`.
- **Create a Adobe Commerce attribute set** (Create). Create attribute set from data. Send the body wrapped as `{"attributeSet": {...}}`.
- **List all Adobe Commerce attribute sets** (List). List attribute sets. Filter with filter_field, filter_value and filter_condition_type; sort with sort_field and sort_direction. The connector pages automatically (`limit`, default 100, max 300). Raw searchCriteria[filter_groups][N] params also work (see the readme).
- **Get single Adobe Commerce attribute set by ID** (Get). Retrieve attribute set information based on given ID. `id` is the Magento `attributeSetId`.
- **Update a Adobe Commerce attribute set by ID** (Update). Save attribute set data. `id` is the Magento `attributeSetId`. Send the body wrapped as `{"attributeSet": {...}}`.
- **Delete a Adobe Commerce attribute set by ID** (Delete). Remove attribute set by given ID. `id` is the Magento `attributeSetId`.
- **Create a Adobe Commerce base price** (Create). Add or update product base prices (`{"prices": [{sku, price, store_id}]}`). Invalid items are returned in the response and not saved.
- **Adobe Commerce base prices search** (Search). Get base prices for SKUs (`{"skus": [..]}`). Fails if any SKU is not found.
- **List all Adobe Commerce bundle product children** (List). Get all children for Bundle product.
- **Update a Adobe Commerce bundle product child by ID** (Update). Update one of bundle product children. `id` is the child product SKU for delete, the link ID for update. Send the body wrapped as `{"linkedProduct": {...}}`.
- **Create a Adobe Commerce bundle product child** (Create). Add child product to specified Bundle option by product sku. Send the body wrapped as `{"linkedProduct": {...}}`.
- **Delete a Adobe Commerce bundle product child by ID** (Delete). Remove product from Bundle product option. `id` is the child product SKU for delete, the link ID for update.
- **Create a Adobe Commerce bundle product option** (Create). Add new option for bundle product. Send the body wrapped as `{"option": {...}}`.
- **Update a Adobe Commerce bundle product option by ID** (Update). Update an option of a bundle product. `id` is the Magento `optionId`. Send the body wrapped as `{"option": {...}}`.
- **List all Adobe Commerce bundle product options** (List). Get all options for bundle product.
- **Get single Adobe Commerce bundle product option by ID** (Get). Get option for bundle product. `id` is the Magento `optionId`.
- **Delete a Adobe Commerce bundle product option by ID** (Delete). Remove bundle option. `id` is the Magento `optionId`.
- **List all Adobe Commerce carts** (List). List carts (quotes), e.g. for abandoned-cart reporting. Read only. Filter with filter_field, filter_value and filter_condition_type; sort with sort_field and sort_direction. The connector pages automatically (`limit`, default 100, max 300). Raw searchCriteria[filter_groups][N] params also work (see the readme).
- **Get single Adobe Commerce cart by ID** (Get). Enables an administrative user to return information for a specified cart. `id` is the cart (quote) ID.
- **Create a Adobe Commerce category** (Create). Create category service. Send the body wrapped as `{"category": {...}}`.
- **List all Adobe Commerce categories** (List). List categories. Filter with filter_field, filter_value and filter_condition_type; sort with sort_field and sort_direction. The connector pages automatically (`limit`, default 100, max 300). Raw searchCriteria[filter_groups][N] params also work (see the readme).
- **Get single Adobe Commerce category by ID** (Get). Get info about category by category id. `id` is the Magento `categoryId`.
- **Delete a Adobe Commerce category by ID** (Delete). Delete category by identifier. `id` is the Magento `categoryId`.
- **Update a Adobe Commerce category by ID** (Update). Update a category. `id` is the Magento `id`. Send the body wrapped as `{"category": {...}}`.
- **List all Adobe Commerce category attribute options** (List). Retrieve list of attribute options.
- **List all Adobe Commerce category attributes** (List). List category attributes. Filter with filter_field, filter_value and filter_condition_type; sort with sort_field and sort_direction. The connector pages automatically (`limit`, default 100, max 300). Raw searchCriteria[filter_groups][N] params also work (see the readme).
- **Get single Adobe Commerce category attribute by ID** (Get). Retrieve specific attribute. `id` is the attribute code.
- **Adobe Commerce category moves bulk update** (Update). Move a category (query `category_id`) under a new parent (`parentId`, optional `afterId`).
- **List all Adobe Commerce category products** (List). Get products assigned to category.
- **Create a Adobe Commerce category product** (Create). Assign a product to the required category. Send the body wrapped as `{"productLink": {...}}`.
- **Delete a Adobe Commerce category product by ID** (Delete). Remove the product assignment from the category by category id and sku. `id` is the product SKU to unassign.
- **List all Adobe Commerce category tree** (List). Get the category tree. Optional `rootCategoryId` and `depth`. Returns one nested tree object (children_data).
- **Create a Adobe Commerce cms block** (Create). Save block. Send the body wrapped as `{"block": {...}}`.
- **List all Adobe Commerce cms blocks** (List). List cms blocks. Filter with filter_field, filter_value and filter_condition_type; sort with sort_field and sort_direction. The connector pages automatically (`limit`, default 100, max 300). Raw searchCriteria[filter_groups][N] params also work (see the readme).
- **Get single Adobe Commerce cms block by ID** (Get). Retrieve block. `id` is the Magento `blockId`.
- **Delete a Adobe Commerce cms block by ID** (Delete). Delete block by ID. `id` is the Magento `blockId`.
- **Update a Adobe Commerce cms block by ID** (Update). Save block. `id` is the Magento `id`. Send the body wrapped as `{"block": {...}}`.
- **Create a Adobe Commerce cms page** (Create). Save page. Send the body wrapped as `{"page": {...}}`.
- **List all Adobe Commerce cms pages** (List). List cms pages. Filter with filter_field, filter_value and filter_condition_type; sort with sort_field and sort_direction. The connector pages automatically (`limit`, default 100, max 300). Raw searchCriteria[filter_groups][N] params also work (see the readme).
- **Update a Adobe Commerce cms page by ID** (Update). Save page. `id` is the Magento `id`. Send the body wrapped as `{"page": {...}}`.
- **Get single Adobe Commerce cms page by ID** (Get). Retrieve page. `id` is the Magento `pageId`.
- **Delete a Adobe Commerce cms page by ID** (Delete). Delete page by ID. `id` is the Magento `pageId`.
- **Create a Adobe Commerce configurable product child** (Create). Link a simple product to a configurable product (query `sku`; body `childSku`).
- **List all Adobe Commerce configurable product children** (List). Get all children for Configurable product.
- **Delete a Adobe Commerce configurable product child by ID** (Delete). Unlink a child product from a configurable product (query `sku`). `id` is the child product SKU. Removing the last child also removes the product's configurable options.
- ...and 165 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
