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.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me the attribute sets that have no attributes assigned
Working in Adobe Commerce with Elaichi
-
List all Adobe Commerce attribute set attributes
-
List all Adobe Commerce attribute set groups
-
List all Adobe Commerce attribute sets
How to connect Adobe Commerce to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Adobe Commerce MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Adobe Commerce MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Adobe Commerce through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Adobe Commerce is logged.
-
Merchandising
Set up a new product line's attributes
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.
-
Pricing
Push base prices across a range
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.
-
Ecommerce
Build a bundle without the admin
Add options and child products to a bundle, adjust them, and remove the ones that are out of stock, all from a chat window.
-
Support
Look up a shopper's cart mid-chat
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.
-
Operations
Audit attribute sets before a cleanup
List every attribute set and its groups, spot the duplicates and the empty ones, and delete what nobody uses.
-
Marketing
Check a bundle before the campaign goes out
List the options and children of a bundle to confirm the landing page matches what Adobe Commerce will actually sell.
Try asking
- “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”
What connecting Adobe Commerce gets you
6 screens from Elaichi, each doing one job for your Adobe Commerce account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about carts and prices in plain words.
Get answers from live Adobe Commerce attribute sets, bundles and carts, not a stale export.
Copy the endpoint
AI apps
One endpoint reaches Adobe Commerce from every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
215 Adobe Commerce tools, no code to write.
Attribute sets, base prices, bundle products and carts, listed with their resources and methods.
Toolboxes
Every team gets its own Adobe Commerce toolbox.
Merchandising shapes attribute sets, pricing sets base prices, support looks up carts.
Shared connections
Teammates use the connection, never the API key.
One person connects Adobe Commerce, shares it with teams, and nobody else handles a credential.
Audit log
Every Adobe Commerce call is written down.
When, who, what happened, type and resource, for every attribute set, price and cart.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Adobe Commerce digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch attribute sets
Adobe Commerce
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Adobe Commerce
Queued
Workflows
A schedule starts the work, a person approves.
Carts are fetched, grouped and drafted into a digest, approved, then posted to Adobe Commerce.
Adobe Commerce health
Refreshed 4 minutes ago · every 15 minutes · from the attribute sets collection
Attribute sets
1,284 ↓ 12%
Base prices
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Attribute sets created
Last 14 days
By team
Share of activity
Merchandising 34%
Pricing 27%
Support 21%
EU storefront 18%
Collections and dashboards
Adobe Commerce health, computed without a model.
Four metrics, carts created over 14 days and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Adobe Commerce tools for your AI agents
215 tools are ready to call through Elaichi's MCP endpoint the moment you connect Adobe Commerce, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Adobe Commerce in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot