# Magento 1 MCP connector

The Magento 1 connector brings your store's orders, customers, addresses, categories and product images to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, with each person signed in as themselves and every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Magento 1 |
| Category | Ecommerce |
| AI tools | 179 |
| 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 Magento 1 is connected

- Show me order 100012345 with its items and shipping address
- Add a comment to order 100012345 saying the carrier is delayed
- Which products are in the Summer Sale category right now

## Connect Magento 1 in Elaichi

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

1. Open Connections, choose Add connection, and pick Magento 1.
2. Optionally set Share with, then press Connect.
3. Paste a Magento 1 API key. One person generates a token in Magento 1 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 Magento 1 tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Magento 1 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.

## Magento 1 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`.

## Magento 1 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.

## Magento 1 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.

## Magento 1 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 Magento 1 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 Magento 1 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 Magento 1 through Elaichi

### Look up an order while the customer waits

Support. Ask for the order by number and get its items, shipping address and comment history in one answer. No switching tabs in the Magento 1 admin while the customer holds.

### Fix a shipping address before it ships

Support. When a customer emails a corrected street or postcode, update the address on their Magento 1 account from the conversation. The old address is replaced and the change is logged under your name.

### Leave a note on an order

Operations. Record a carrier delay, a partial shipment or a call with the customer as a comment on the Magento 1 order. The next person who opens it sees what happened.

### Set up a new category for a launch

Merchandising. Create the category in Magento 1 and check which products already sit in neighboring categories before the range goes live. Retire an empty category when the season ends.

### Add product images in bulk

Catalog. Hand over a list of SKUs and image files and have each one attached to the right Magento 1 product. Review what is already on a product before adding more.

### Pull a customer list for a campaign

Marketing. Ask for Magento 1 customers by region or sign-up date and get names and contact details ready for the next send. Clean up duplicate or test accounts along the way.

## Elaichi vs Zapier MCP vs Composio for Magento 1

All three can connect Magento 1 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 Magento 1 tools | Allow or restrict single Magento 1 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 Magento 1 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 Magento 1 to Claude?

Connect Magento 1 in Elaichi by pasting the API key from your Magento 1 admin. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Magento 1 is ready to use from Claude.

### Does Magento 1 work with ChatGPT and Cursor as well as Claude?

Yes. Once Magento 1 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 Magento 1 once and every client picks it up.

### What can an AI agent actually do with my Magento 1 data?

It can find an order and show its items, addresses and comments, add a note to an order, and look up or update a customer and their addresses. It can also list the products in a category, create or remove a category, and add images to a product. Short, concrete asks work better than long sentences: "show me order 100012345 with its items" gets a clean answer from Magento 1.

### Does connecting Magento 1 give the AI access to my whole store?

No. Every call to Magento 1 runs inside the access of the person who signed in to Elaichi, so an agent sees the orders, customers and categories that person is allowed to work with and nothing beyond. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

### Can my team share one Magento 1 connection?

Yes. One person connects Magento 1 with the API key and shares the connection with a team, and nobody else ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so every order lookup or address change in the audit log is tied to the person who made it.

### Can I stop an agent from deleting or changing things in Magento 1?

Yes. Restrictions apply per action, so you can allow reading Magento 1 orders and customers while restricting deleting a customer, removing an address or deleting a category, on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Magento 1 connection when someone leaves?

Offboarding that person in Elaichi ends their access to Magento 1 at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Magento 1 connection keeps working for everyone else on the team. If you ever want to remove Magento 1 entirely, disconnecting it once in Elaichi removes it from every client.

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

Yes. Magento 1 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 Magento 1?

Yes. Both let Claude, ChatGPT or Cursor use Magento 1. 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 Magento 1 call.

### How is Elaichi different from Composio for Magento 1?

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 Magento 1: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 179 Magento 1 tools

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

- **List all Magento 1 category products** (List). Products in a category (Magento REST GET /api/rest/products/category/:category_id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: category_id. The connector follows the pages (up to 100 records each, in id order).
- **List all Magento 1 customer addresses** (List). Addresses of a customer (Magento REST GET /api/rest/customers/:customer_id/addresses). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: customer_id.
- **Get single Magento 1 customer address by ID** (Get). Customer address (Magento REST GET /api/rest/customers/addresses/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **Create a Magento 1 customer address** (Create). Add a customer address (Magento REST POST /api/rest/customers/:customer_id/addresses). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: customer_id.
- **Update a Magento 1 customer address by ID** (Update). Update a customer address (Magento REST PUT /api/rest/customers/addresses/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **Delete a Magento 1 customer address by ID** (Delete). Delete a customer address (Magento REST DELETE /api/rest/customers/addresses/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **List all Magento 1 customers** (List). Customers (Magento REST GET /api/rest/customers). Needs the REST OAuth fields on the connection and a REST role that allows it. The connector follows the pages (up to 100 records each, in id order).
- **Get single Magento 1 customer by ID** (Get). Customer (Magento REST GET /api/rest/customers/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **Update a Magento 1 customer by ID** (Update). Update a customer (Magento REST PUT /api/rest/customers/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **Delete a Magento 1 customer by ID** (Delete). Delete a customer (Magento REST DELETE /api/rest/customers/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **List all Magento 1 order addresses** (List). Addresses of an order (Magento REST GET /api/rest/orders/:order_id/addresses). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: order_id.
- **Get single Magento 1 order address by ID** (Get). Order address (id = billing or shipping) (Magento REST GET /api/rest/orders/:order_id/addresses/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id, order_id.
- **List all Magento 1 order comments** (List). Comments of an order (Magento REST GET /api/rest/orders/:order_id/comments). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: order_id.
- **Get single Magento 1 order comment by ID** (Get). Order comment (Magento REST GET /api/rest/orders/comments/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **Create a Magento 1 order comment** (Create). Add an order comment (Magento REST POST /api/rest/orders/:order_id/comments). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: order_id.
- **List all Magento 1 order items** (List). Items of an order (Magento REST GET /api/rest/orders/:order_id/items). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: order_id.
- **List all Magento 1 orders** (List). Orders (Magento REST GET /api/rest/orders). Needs the REST OAuth fields on the connection and a REST role that allows it. The connector follows the pages (up to 100 records each, in id order).
- **Get single Magento 1 order by ID** (Get). Order (Magento REST GET /api/rest/orders/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **List all Magento 1 product categories** (List). Categories of a product (Magento REST GET /api/rest/products/:product_id/categories). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: product_id.
- **Create a Magento 1 product category** (Create). Assign a product to a category (Magento REST POST /api/rest/products/:product_id/categories). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: product_id.
- **Delete a Magento 1 product category by ID** (Delete). Unassign a product from a category (Magento REST DELETE /api/rest/products/:product_id/categories/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id, product_id.
- **List all Magento 1 product images** (List). Images of a product (Magento REST GET /api/rest/products/:product_id/images). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: product_id.
- **Get single Magento 1 product image by ID** (Get). Product image (Magento REST GET /api/rest/products/:product_id/images/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id, product_id.
- **Create a Magento 1 product image** (Create). Add a product image (Magento REST POST /api/rest/products/:product_id/images). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: product_id.
- **Update a Magento 1 product image by ID** (Update). Update a product image (Magento REST PUT /api/rest/products/:product_id/images/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id, product_id.
- **Delete a Magento 1 product image by ID** (Delete). Remove a product image (Magento REST DELETE /api/rest/products/:product_id/images/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id, product_id.
- **List all Magento 1 product websites** (List). Websites of a product (Magento REST GET /api/rest/products/:product_id/websites). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: product_id.
- **Create a Magento 1 product website** (Create). Assign a product to a website (Magento REST POST /api/rest/products/:product_id/websites). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: product_id.
- **Delete a Magento 1 product website by ID** (Delete). Unassign a product from a website (Magento REST DELETE /api/rest/products/:product_id/websites/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id, product_id.
- **List all Magento 1 products** (List). Products (Magento REST GET /api/rest/products). Needs the REST OAuth fields on the connection and a REST role that allows it. The connector follows the pages (up to 100 records each, in id order).
- **Get single Magento 1 product by ID** (Get). Product (Magento REST GET /api/rest/products/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **Create a Magento 1 product** (Create). Product (Magento REST POST /api/rest/products). Needs the REST OAuth fields on the connection and a REST role that allows it.
- **Update a Magento 1 product by ID** (Update). Product (Magento REST PUT /api/rest/products/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **Delete a Magento 1 product by ID** (Delete). Product (Magento REST DELETE /api/rest/products/:id). Needs the REST OAuth fields on the connection and a REST role that allows it. Required: id.
- **List all Magento 1 rest connection checks** (List). Check the REST (OAuth 1.0a) credentials with a one-product read. The connector calls it when an account connects. Returns ok true or the error.
- **List all Magento 1 rpc API resources** (List). List the API resources and methods this API user's role can call. Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only).
- **Create a Magento 1 rpc attribute set attribute** (Create). Product attribute sets API: Add attribute into attribute set (Magento API catalog_product_attribute_set.attributeAdd). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: attribute_id, attribute_set_id.
- **Magento 1 rpc attribute set attributes bulk delete** (Delete). Product attribute sets API: Remove attribute from attribute set (Magento API catalog_product_attribute_set.attributeRemove). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: attribute_id, attribute_set_id.
- **Create a Magento 1 rpc attribute set group** (Create). Product attribute sets API: Add group into attribute set (Magento API catalog_product_attribute_set.groupAdd). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: attribute_set_id, group_name.
- **Update a Magento 1 rpc attribute set group by ID** (Update). Product attribute sets API: Rename existing group (Magento API catalog_product_attribute_set.groupRename). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). The id is group_id. Required: id, group_name.
- **Delete a Magento 1 rpc attribute set group by ID** (Delete). Product attribute sets API: Remove group from attribute set (Magento API catalog_product_attribute_set.groupRemove). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). The id is attribute_group_id. Required: id.
- **List all Magento 1 rpc attribute sets** (List). Product attribute sets API: Retrieve product attribute sets (Magento API catalog_product_attribute_set.list). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only).
- **Create a Magento 1 rpc attribute set** (Create). Product attribute sets API: Create attribute set based on another set (Magento API catalog_product_attribute_set.create). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: attribute_set_name, skeleton_set_id.
- **Delete a Magento 1 rpc attribute set by ID** (Delete). Product attribute sets API: Remove attribute set (Magento API catalog_product_attribute_set.remove). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). The id is attribute_set_id. Required: id.
- **Magento 1 rpc calls execute** (Execute). Call any Magento API method, including ones added by extensions: api_path is resource.method (e.g. catalog_product.list) and args the positional arguments as an array. Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: api_path.
- **Create a Magento 1 rpc cart coupon** (Create). Shopping cart ability to set coupon code: Add coupon code for shopping cart (Magento API cart_coupon.add). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: quote_id, coupon_code.
- **Magento 1 rpc cart coupons bulk delete** (Delete). Shopping cart ability to set coupon code: Remove coupon code from shopping cart (Magento API cart_coupon.remove). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: quote_id.
- **Create a Magento 1 rpc cart customer address** (Create). Customer Information: Set customer's addresses in shopping cart (Magento API cart_customer.addresses). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: quote_id, customer_address_data.
- **Create a Magento 1 rpc cart customer** (Create). Customer Information: Set customer for shopping cart (Magento API cart_customer.set). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). Required: quote_id, customer_data.
- **Get single Magento 1 rpc cart license by ID** (Get). Shopping Cart: Get terms and conditions (Magento API cart.license). Needs the OpenMage API user fields on the connection (JSON-RPC, OpenMage only). The id is quote_id. Required: id.
- ...and 129 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
