Ongoing WMS MCP connector
The Ongoing WMS connector brings articles, article items, batches and dangerous goods into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can look up and update warehouse stock by asking in plain language.
- Connects with an API key
- Free 14-day trial
- No credit card
Which article items are locked in the Stockholm warehouse right now?
Working in Ongoing WMS with Elaichi
-
List all Ongoing WMS article categories
-
List all Ongoing WMS article classes
-
List all Ongoing WMS article dangerous goods
How to connect Ongoing WMS to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Ongoing WMS 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.
Ongoing WMS 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.
Ongoing WMS 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.
Ongoing WMS 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.
Ongoing WMS 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 Ongoing WMS 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 Ongoing WMS through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Ongoing WMS is logged.
-
Warehouse operations
Find where a batch of stock sits
Ask which article items belong to a given batch and what status each one carries, without opening Ongoing WMS and clicking through filters. Lock an item that needs holding back while the question is still open.
-
Ecommerce
Check an article before it goes live
Pull an article's category, group and class in one ask so the product page matches what the warehouse actually holds. Attach a spec sheet or image as an article file while you are at it.
-
Compliance
Keep dangerous goods records straight
List every article flagged as dangerous goods, see which classification it carries, and register a new one when a hazardous product arrives. Nothing ships without the paperwork behind it.
-
Quality
Put a quarantine on suspect items
Create a quarantine status in Ongoing WMS and assign it to the article items from a failed inspection, then list everything still under that status at the end of the week.
-
Purchasing
See what an article is made of
Look up the materials behind an article by its number, then check which article group and class it belongs to before placing a reorder with the supplier.
-
Support
Answer a stock question on the call
Search article items by name or number while the customer is still on the line, and read back whether the item is available, locked or sitting in a held batch.
Try asking
- “Which article items are locked in the Stockholm warehouse right now?”
- “List every article flagged as dangerous goods and its class.”
- “Show me article items from batch 2411 with a quarantine status.”
What connecting Ongoing WMS gets you
6 screens from Elaichi, each doing one job for your Ongoing WMS account.
Ask Elaichi to work across your apps.
Which article items are locked in the Stockholm warehouse right now?
List every article flagged as dangerous goods and its class.
Show me article items from batch 2411 with a quarantine status.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about article items in plain language.
Get answers from live Ongoing WMS batches, statuses and locks, not a stale export.
Copy the endpoint
AI apps
Ongoing WMS in every client, one endpoint.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Tool catalog
All 157 Ongoing WMS tools, no code needed.
Articles, article items, batches, dangerous goods and files, covered without writing a line.
Toolboxes
Every team gets its own Ongoing WMS toolbox.
Warehouse, compliance and support each see the tools that match their job.
Shared connections
Share Ongoing WMS without sharing the key.
One person connects, teammates work through it, and nobody else sees the credential.
Audit log
Know who locked which article item.
Every Ongoing WMS call is logged with who, when, what happened and which resource.
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.
Ongoing WMS digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch articles
Ongoing WMS
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
Ongoing WMS
Queued
Workflows
A schedule starts the work, not a question.
Article items are fetched, grouped and summarized, a person approves, and Ongoing WMS is updated.
Ongoing WMS health
Refreshed 4 minutes ago · every 15 minutes · from the articles collection
Articles
1,284 ↓ 12%
Article items
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Articles created
Last 14 days
By team
Share of activity
Stockholm warehouse 34%
Oslo warehouse 27%
Compliance 21%
Ecommerce 18%
Collections and dashboards
Ongoing WMS numbers, computed without a model.
Article items created over 14 days, broken down by team, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Ongoing WMS
All three can connect Ongoing WMS 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 Ongoing WMS tools | Allow or restrict single Ongoing WMS 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 Ongoing WMS 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.
Ongoing WMS tools for your AI agents
157 tools are ready to call through Elaichi's MCP endpoint the moment you connect Ongoing WMS, 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 Ongoing WMS to Claude?
Open Elaichi, choose Ongoing WMS and paste in the API key from your Ongoing WMS account. 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 as the endpoint. Sign in with your own Elaichi login and Ongoing WMS is ready to ask questions of.
Does Ongoing WMS work with ChatGPT and Cursor as well as Claude?
Yes. Once Ongoing WMS 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 Ongoing WMS once and every client picks it up.
What can an AI agent actually do with my Ongoing WMS data?
It can search article items by name or number, list the articles in a category or group, show which items belong to a batch, and tell you what status or lock an item carries. It can also create article classes, batches, item locks and statuses, register dangerous goods and attach files to an article in Ongoing WMS. Short, concrete asks such as "locked items in batch 2411" work better than long paragraphs.
Does connecting Ongoing WMS give the AI everything in my warehouse?
No. Every call into Ongoing WMS runs as the person who signed in, so the agent sees only the articles, items and batches that person's Ongoing WMS account can already see. Elaichi can narrow that further with roles and restrictions, but it never widens it beyond what Ongoing WMS itself allows.
Can I stop an agent from deleting or changing things in Ongoing WMS?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting article classes or creating item locks in Ongoing WMS for a role or for one person while leaving lookups open. 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 an Ongoing WMS connection when someone leaves?
Offboarding that person in Elaichi ends their access to Ongoing WMS at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Ongoing WMS connection keeps working for everyone else on the team. If you ever want Ongoing WMS gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the Ongoing WMS MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Ongoing WMS 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 Ongoing WMS?
Yes. Both let Claude, ChatGPT or Cursor use Ongoing WMS. 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 Ongoing WMS call.
How is Elaichi different from Composio for Ongoing WMS?
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 Ongoing WMS: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Ongoing WMS 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