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.
- Connects with an API key
- Free 14-day trial
- No credit card
Which QLS fulfillment orders are on backorder this week?
Working in QLS with Elaichi
-
List all QLS brands
-
Get single QLS brand by ID
-
List all QLS companies
How to connect QLS to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
QLS 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.
QLS 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.
QLS 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.
QLS 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.
QLS 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 QLS 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 QLS through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in QLS is logged.
-
Fulfillment
Raise a fulfillment order from a chat
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.
-
Support
Answer where is my order in seconds
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.
-
Support
Cancel an order before it leaves
When a customer calls to cancel, ask the agent to cancel the QLS fulfillment order on the spot and confirm it is done.
-
Purchasing
Spot backorders before customers notice
List every QLS fulfillment order sitting on backorder, group it by product, and see what to reorder first.
-
Catalog
Keep barcodes and master cartons tidy
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.
-
Operations
Check stock across brands and companies
Pull current QLS product stock for a brand or a company, compare it with open orders, and decide what can be promised this week.
Try asking
- “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.”
What connecting QLS gets you
6 screens from Elaichi, each doing one job for your QLS account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about QLS orders in plain language.
Three starter prompts pull live fulfillment orders, stock and backorders from QLS.
Copy the endpoint
AI apps
One endpoint connects QLS to every client.
Claude, ChatGPT and Cursor reach QLS through one governed endpoint, no SDK, no shared key.
Tool catalog
64 QLS tools, no code to write.
Fulfillment orders, product stock, barcodes and master cartons, cataloged and ready without custom code.
Toolboxes
Every team gets its own QLS toolbox.
Scope fulfillment, support and catalog teams to the QLS tools they actually use.
Shared connections
Share a QLS connection, never the key.
One person connects QLS, teammates work through it without ever seeing the API key.
Audit log
Every QLS action is logged and named.
See when, who, and which fulfillment order or barcode changed, in an append-only log.
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.
QLS digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch fulfillment orders
QLS
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
QLS
Queued
Workflows
A schedule starts real QLS work.
Backorders are fetched, grouped, drafted into a digest, approved by a person, then posted back.
QLS health
Refreshed 4 minutes ago · every 15 minutes · from the fulfillment orders collection
Fulfillment orders
1,284 ↓ 12%
Products
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Fulfillment orders created
Last 14 days
By team
Share of activity
Fulfillment 34%
Support 27%
Catalog 21%
Purchasing 18%
Collections and dashboards
QLS health, computed without a model.
Four metrics, 14 days of fulfillment orders created, and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
QLS tools for your AI agents
64 tools are ready to call through Elaichi's MCP endpoint the moment you connect QLS, 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 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 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.
Put QLS 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