# QLS MCP connector

Connecting QLS to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent create and update QLS fulfillment orders, check stock and backorders, and manage product barcodes and master cartons, with every action logged.

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

## Facts

| | |
| --- | --- |
| Application | QLS |
| Category | Ecommerce |
| AI tools | 64 |
| 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 QLS is connected

- Which QLS fulfillment orders are on backorder this week?
- Show current stock for our Nova brand products in QLS.
- Create a fulfillment order for the Rotterdam wholesale shipment.

## Connect QLS in Elaichi

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

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

## QLS 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.

## QLS 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`.

## QLS 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.

## QLS 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.

## QLS 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 QLS 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 QLS 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 QLS through Elaichi

### Raise a fulfillment order from a chat

Fulfillment. Describe the shipment and the agent creates the QLS fulfillment order with the right products and quantities, then updates it if the customer changes their mind before it ships.

### Answer where is my order in seconds

Support. Look up a QLS fulfillment order by its reference, see its current status and products, and tell the customer what is happening without opening another tab.

### Cancel an order before it leaves

Support. When a customer calls to cancel, ask the agent to cancel the QLS fulfillment order on the spot and confirm it is done.

### Spot backorders before customers notice

Purchasing. List every QLS fulfillment order sitting on backorder, group it by product, and see what to reorder first.

### Keep barcodes and master cartons tidy

Catalog. Add a new barcode for a product, fix a wrong one, or set up master carton details so the warehouse scans the right thing on arrival.

### Check stock across brands and companies

Operations. Pull current QLS product stock for a brand or a company, compare it with open orders, and decide what can be promised this week.

## Elaichi vs Zapier MCP vs Composio for QLS

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

Connect QLS in Elaichi first by pasting your QLS API key, which takes about a minute. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate; the QLS API key is the only thing you need.

### Does QLS work with ChatGPT and Cursor as well as Claude?

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

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

An agent can create and update QLS fulfillment orders, cancel them, list which orders are on backorder, and look up product stock, brands, companies and contacts. It can also add, change or remove product barcodes and master carton details. Short, concrete asks such as cancel order 4821 or show backorders for brand Nova work better than long sentences.

### Does connecting QLS give the AI everything in my QLS account?

No. Every call to QLS runs inside the access of the person who signed in to Elaichi, so an agent can only see and change what that person already can in QLS. Elaichi can narrow that access further with restrictions, and it never widens it.

### Can my team share one QLS connection?

Yes. One person connects QLS with the API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created or cancelled a QLS fulfillment order, not a shared account.

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

Yes. In Elaichi you can restrict individual actions in QLS, such as cancelling fulfillment orders or deleting barcodes, 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 a QLS connection when someone leaves?

Offboarding a person in Elaichi ends their access to QLS at once, in every client they used. A QLS connection shared with the team keeps working for everyone else. If you want QLS gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

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

Yes. QLS 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 QLS?

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

### How is Elaichi different from Composio for QLS?

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

## All 64 QLS tools

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

- **List all QLS brands** (List). Get a list of brands.
- **Get single QLS brand by ID** (Get). Get a brand. Required: id.
- **List all QLS companies** (List). Get a list of companies. The connector pages through all results.
- **Get single QLS company by ID** (Get). Get a company. Required: id.
- **Update a QLS contact by ID** (Update). Update a contact. Required: id.
- **List all QLS fulfillment order backorders** (List). List fulfilment orders in backorder. The connector pages through all results.
- **Create a QLS fulfillment order product** (Create). Create an order product. Required: order_id.
- **Get single QLS fulfillment order product by ID** (Get). Get an order product. Required: id, order_id.
- **Update a QLS fulfillment order product by ID** (Update). Update an order product. Required: id, order_id.
- **List all QLS fulfillment orders** (List). List fulfilment orders, filterable by created time, shop integration and brand. The connector pages through all results.
- **Get single QLS fulfillment order by ID** (Get). Get a fulfilment order. Required: id.
- **Create a QLS fulfillment order** (Create). Create an order. Required: brand_id.
- **Update a QLS fulfillment order by ID** (Update). Update an order. Required: id.
- **QLS fulfillment orders cancel** (Cancel). Cancel an order. Required: order_id.
- **Update a QLS fulfillment product barcode by ID** (Update). Update an extra barcode. Required: id, product_id.
- **Delete a QLS fulfillment product barcode by ID** (Delete). Delete an extra barcode. Required: id, product_id.
- **List all QLS fulfillment product barcodes** (List). Get a list of extra barcodes. Required: product_id.
- **Create a QLS fulfillment product barcode** (Create). Create an extra barcode. Required: product_id.
- **List all QLS fulfillment product master cartons** (List). Get a master carton. Required: product_id.
- **Create a QLS fulfillment product master carton** (Create). Create a master carton. Required: product_id.
- **Update a QLS fulfillment product master carton by ID** (Update). Update a master carton. Required: id, product_id.
- **Delete a QLS fulfillment product master carton by ID** (Delete). Delete a master carton. Required: id, product_id.
- **List all QLS fulfillment product stock** (List). Get the stock of one fulfilment product. Required: fulfillment_product_id.
- **List all QLS fulfillment product stocks** (List). List the stock of all fulfilment products, filterable by created/modified time. The connector pages through all results.
- **List all QLS fulfillment product suppliers** (List). Get a list of suppliers for a product. Required: product_id.
- **Create a QLS fulfillment product supplier** (Create). Connect a supplier to a product. Connect a supplier to a product. Creates supplier if supplier does not exist. Required: product_id, supplierName.
- **Delete a QLS fulfillment product supplier by ID** (Delete). Disconnect a supplier from a product. Required: id, product_id.
- **List all QLS fulfillment products** (List). List fulfilment products (SKUs stored at QLS), with stock, filterable by EAN, SKU and stock amounts. The connector pages through all results.
- **Get single QLS fulfillment product by ID** (Get). Get a fulfilment product. Required: id.
- **Create a QLS fulfillment product** (Create). Create a product. Required: name.
- **Update a QLS fulfillment product by ID** (Update). Update a product. Required: id.
- **Delete a QLS fulfillment product by ID** (Delete). Delete a product. Required: id.
- **QLS fulfillment products merge** (Merge). Merge other products into this product. Required: product_id.
- **List all QLS in transit purchase orders** (List). List purchase orders in transit to the warehouse. The connector pages through all results.
- **Create a QLS order return** (Create). Create a return for a fulfilment order. Required: order_id.
- **List all QLS parcel products** (List). List the parcel service products (carrier products) of the company.
- **List all QLS product backorders** (List). Get a list of products in backorder.
- **List all QLS product service points** (List). Get a list of service points for a product. Required: product_id, country, postal_code.
- **List all QLS purchase orders** (List). List purchase orders (inbound deliveries), filterable by status and created/modified time. The connector pages through all results.
- **Get single QLS purchase order by ID** (Get). Get a purchase order. Required: id.
- **QLS purchase orders cancel** (Cancel). Cancel a purchase order. Required: purchase_order_id.
- **Create a QLS purchase order** (Create). Create a purchase order (announce an inbound delivery).
- **Update a QLS purchase order by ID** (Update). Update a purchase order. Required: id.
- **List all QLS returns** (List). List returns, filterable by status and created/processed time. The connector pages through all results.
- **Create a QLS return** (Create). Create a return. Required: brand_id.
- **Get single QLS return by ID** (Get). Get a return. Required: id.
- **QLS returns archive** (Archive). Archive a return. Required: return_id.
- **List all QLS service points** (List). Get a list of service points. Required: country, postal_code.
- **List all QLS shipment returns** (List). Get a return shipment for shipment. Required: shipment_id.
- **Create a QLS shipment** (Create). Create a parcel shipment (and its label). Required: brand_id, product_combination_id, receiver_contact.
- ...and 14 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
