# Mirakl Connect MCP connector

Connect Mirakl Connect to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can list orders, approve returns, answer customer conversations and update products, each person acting as themselves with every action logged.

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

## Facts

| | |
| --- | --- |
| Application | Mirakl Connect |
| Category | Ecommerce |
| AI tools | 24 |
| Authentication | App credentials |
| 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 Mirakl Connect is connected

- Which orders are waiting for approval today?
- Summarize unanswered customer conversations from this week.
- List open returns and draft a reply for each customer.

## Connect Mirakl Connect in Elaichi

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

1. Open Connections, choose Add connection, and pick Mirakl Connect.
2. Optionally set Share with, then press Connect.
3. Paste your Mirakl Connect app credentials. Mirakl Connect authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

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

## Mirakl Connect 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.

## Mirakl Connect 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`.

## Mirakl Connect 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.

## Mirakl Connect 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.

## Mirakl Connect 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 Mirakl Connect 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 Mirakl Connect 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 Mirakl Connect through Elaichi

### Approve the morning's orders in one pass

Operations. Ask for every Mirakl Connect order waiting on approval, check the details, and approve the ones that are ready. Cancel the ones you cannot fulfil without opening each order by hand.

### Answer customer conversations without switching tabs

Support. Pull up open Mirakl Connect conversations, read the thread and the attachments, and send a reply from where you already are. Start a new conversation on an order when a customer has not written first.

### Move returns from requested to closed

Returns. List the returns waiting on you, approve or confirm them, add the return tracking, and close them once the goods are back. The whole return runs through Mirakl Connect without you re-keying anything.

### Update products in bulk from a spreadsheet

Catalog. Paste in a list of changed prices, titles or stock and have the products in Mirakl Connect updated in one go. Remove discontinued products the same way.

### Create shipments and attach the paperwork

Logistics. Create the shipment for an approved Mirakl Connect order and upload the invoice or packing document against it. Check which orders still have no document before the carrier arrives.

### Issue refunds and keep the record straight

Finance. Refund a Mirakl Connect order in part or in full once a return is confirmed, and record the result of each order action so the audit trail matches the ledger.

## Elaichi vs Zapier MCP vs Composio for Mirakl Connect

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

First connect Mirakl Connect in Elaichi by entering your Mirakl Connect app credentials; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Mirakl Connect orders, returns, products and conversations are available in Claude.

### Does Mirakl Connect work with ChatGPT and Cursor as well as Claude?

Yes. Mirakl Connect is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. There is nothing to set up separately for each client.

### What can an AI agent actually do with my Mirakl Connect data?

It can list and approve, cancel or refund Mirakl Connect orders, create shipments and attach order documents, approve, confirm and close returns and add return tracking. It can read and reply to customer conversations, including attachments, and update or remove products in bulk. Short, concrete asks such as "approve order 4471" work better than long sentences.

### Does connecting Mirakl Connect give the AI access to every order and product?

No. Every call runs as the person who signed in, so an agent only sees the Mirakl Connect orders, returns, products and conversations that person could already open. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Mirakl Connect itself allows.

### Can my team share one Mirakl Connect connection?

Yes. One person connects Mirakl Connect with the app credentials and shares the connection with a team in Elaichi, so nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every order approval or refund.

### Can I stop an agent from deleting or changing things in Mirakl Connect?

Yes. Restrictions in Elaichi work per action, so you can restrict bulk product deletion, order cancellation or refunds on a role or on one person while leaving reads open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it on Mirakl Connect whatever the prompt says.

### What happens to a Mirakl Connect connection when someone leaves?

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

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

Yes. Mirakl Connect 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 Mirakl Connect?

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

### How is Elaichi different from Composio for Mirakl Connect?

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

## All 24 Mirakl Connect tools

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

- **Get single Mirakl Connect conversation action by ID** (Get). Check the status of your asynchronous conversation action. Required: id.
- **List all Mirakl Connect conversation attachment contents** (List). Download attachments of a conversation as a ZIP file. Required: conversation_id. Returns a ZIP file, not JSON.
- **Create a Mirakl Connect conversation message** (Create). Create a new message to the customer in a conversation. Required: conversation_id, message_input. Mirakl processes it asynchronously: the response has an action_id; check it with conversation_actions get.
- **List all Mirakl Connect conversation messages** (List). List the messages of a conversation, newest first. Required: conversation_id.
- **Create a Mirakl Connect conversation** (Create). Initiate a new conversation with a customer on a marketplace. Returns an action identifier to track the asynchronous processing. Required: conversation. Mirakl processes it asynchronously: the response has an action_id; check it with conversation_actions get.
- **List all Mirakl Connect conversations** (List). Synchronize Mirakl Connect conversations with your system. The connector follows next_page_token through every page.
- **Create a Mirakl Connect order action result** (Create). Report to Connect the results of actions performed on orders in your system, such as synchronizing back orders. Required: actions.
- **Get single Mirakl Connect order action by ID** (Get). Check the status of an asynchronous action request (e.g., v2-acceptOrderLines) and retrieve any potential errors that occurred during the action processing. We recommend integrating this API asynchronously. Required: id.
- **List all Mirakl Connect order document contents** (List). Download documents of an order as a ZIP file. Required: order_id. Returns a ZIP file, not JSON.
- **Create a Mirakl Connect order document** (Create). Upload a document for an order or its related entities (e.g. returns). Supported document types are : - RETURN_LABEL - CUSTOMER_INVOICE. Required: order_id, file, metadata. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **List all Mirakl Connect order documents** (List). Retrieve documents across orders with pagination support. Each document in the response includes its associated order_id along with metadata such as name, type, size, and last update date. The connector follows next_page_token through every page.
- **Mirakl Connect orders approve** (Approve). Accept or refuse order lines in AWAITING_ACCEPTANCE. Required: order_id, order_lines. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **Mirakl Connect orders cancel** (Cancel). Cancel order lines (all or part) of an order. Required: order_id, cancelations. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **List all Mirakl Connect orders** (List). Synchronize Mirakl Connect orders with your system. We recommend integrating this API in asynchronous mode. You can retrieve all orders updated since the last call, and update your referential accordingly. The connector follows next_page_token through every page.
- **Mirakl Connect orders refund** (Action). Refund order lines (all or part) of an order. Required: order_id, refunds. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **Mirakl Connect products bulk delete** (Delete). Delete one or more products using the product identifiers. Limitations: - Maximum 1000 products per request - For larger deletions, split into multiple requests. Required: products.
- **List all Mirakl Connect products** (List). Retrieve products imported in your Mirakl Connect catalog. Items are sorted by product identifiers. The connector follows next_page_token through every page.
- **Mirakl Connect products bulk upsert** (Upsert). Products are created if they do not already exist. The missing fields in the request remain unchanged on the Mirakl Connect catalog (behaves like a PATCH). Omitted top-elements in the API will remain unchanged.
- **Create a Mirakl Connect return tracking** (Create). Set the tracking information of a return (replaces what is there). Required: return_id. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **Mirakl Connect returns approve** (Approve). Accept a return request. Required: return_id, accepted. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **Mirakl Connect returns confirm** (Action). Confirm that the returned items were received. Required: return_id. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **Mirakl Connect returns close** (Close). Close a return. Required: return_id. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
- **List all Mirakl Connect returns** (List). Synchronize Mirakl Connect returns with your system. We recommend integrating this API in asynchronous mode. You can retrieve all returns updated since the last call, and update your referential accordingly. Required: updated_from. The connector follows next_page_token through every page.
- **Create a Mirakl Connect shipment** (Create). Ship one or more items from the same order within the same package (using the same tracking information). Required: order_id, items. Mirakl processes it asynchronously: the response has an action_id; check it with order_actions get.
