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

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

## Facts

| | |
| --- | --- |
| Application | Ongoing WMS |
| Category | Ecommerce |
| AI tools | 157 |
| 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 Ongoing WMS is connected

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

## Connect Ongoing WMS in Elaichi

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

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

## Ongoing WMS 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.

## Ongoing WMS 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`.

## Ongoing WMS 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.

## Ongoing WMS 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.

## Ongoing WMS 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 Ongoing WMS 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 Ongoing WMS 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 Ongoing WMS through Elaichi

### Find where a batch of stock sits

Warehouse operations. 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.

### Check an article before it goes live

Ecommerce. 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.

### Keep dangerous goods records straight

Compliance. 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.

### Put a quarantine on suspect items

Quality. 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.

### See what an article is made of

Purchasing. 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.

### Answer a stock question on the call

Support. 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.

## 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. Endpoint: 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](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 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 my team share one Ongoing WMS connection?

Yes. One person connects Ongoing WMS with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every article lookup or status change in Ongoing WMS.

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

## All 157 Ongoing WMS tools

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

- **List all Ongoing WMS article categories** (List). Get all article categories. goodsOwnerId comes from the connected account.
- **Create a Ongoing WMS article class assignment** (Create). Set the article classes of an article. Required: article_system_id, articleClassIds.
- **List all Ongoing WMS article classes** (List). Get all article classes. goodsOwnerId comes from the connected account.
- **Create a Ongoing WMS article class** (Create). Create or update an article class. If there is no article class with the specified code, it will be created. Otherwise, the existing article class will be updated. Required: goodsOwnerId, code, name.
- **Update a Ongoing WMS article class by ID** (Update). Update an article class. The ID will be used to identify the article class. Required: id, goodsOwnerId, code, name.
- **Delete a Ongoing WMS article class by ID** (Delete). Delete an article class. This will affect any articles which have previously been assigned to the class. Required: id.
- **Create a Ongoing WMS article dangerous good** (Create). Update the dangerous goods info of an article. Note that the UN number must exist in Ongoing WMS before any articles can be set to that UN number. Required: article_system_id, unNumber.
- **List all Ongoing WMS article dangerous goods** (List). Get dangerous goods info for an article. Required: article_system_id.
- **Create a Ongoing WMS article dangerous goods by number** (Create). Update the dangerous goods info of an article via the article number. Required: goodsOwnerId, articleNumber, dangerousGoods.
- **List all Ongoing WMS article dangerous goods by number** (List). Get dangerous goods info for articles, using article numbers. goodsOwnerId comes from the connected account.
- **List all Ongoing WMS article files** (List). Get all files which are attached to a specific article. Required: article_system_id.
- **Create a Ongoing WMS article file** (Create). Create a new file and attach it to the specified article. Required: article_system_id, fileName, mimeType, fileDataBase64.
- **Update a Ongoing WMS article file by ID** (Update). Update a file which is attached to an article. Required: id, article_system_id, fileName, mimeType, fileDataBase64.
- **Create a Ongoing WMS article files by name** (Create). Create or update a file which is attached to an article. The filename will be used to check if the file already exists. Required: article_system_id, fileName, mimeType, fileDataBase64.
- **List all Ongoing WMS article groups** (List). Get all article groups. goodsOwnerId comes from the connected account.
- **Create a Ongoing WMS article item batch** (Create). Update batch. Required: article_item_id, batchNumber.
- **Create a Ongoing WMS article item lock** (Create). Update "is locked". Required: article_item_id, isLocked.
- **Create a Ongoing WMS article item status assignment** (Create). Update article item status. Required: article_item_id.
- **List all Ongoing WMS article item statuses** (List). Get all article item statuses. goodsOwnerId comes from the connected account.
- **Create a Ongoing WMS article item status** (Create). Create or update an article item status. If there is no article item with the specified code, it will be created. Otherwise, the existing status will be updated. Required: goodsOwnerId, code, name.
- **List all Ongoing WMS article items** (List). Get all article items which match the specified search criteria. The search criteria are specified as query parameters. goodsOwnerId comes from the connected account. The connector pages through all results (500 per page).
- **Ongoing WMS article items search** (Search). Search article items (individual stock items) with a query body. Required: goodsOwnerId.
- **List all Ongoing WMS article materials** (List). Get article materials for a specific article. Required: article_system_id.
- **List all Ongoing WMS article materials by number** (List). Get article materials for several articles at the same time. goodsOwnerId comes from the connected account. The connector pages through all results (500 per page).
- **Create a Ongoing WMS article storage class** (Create). Update storage class. Required: article_system_id, storageClassName.
- **Ongoing WMS article storage classes bulk delete** (Delete). Remove the storage class of an article. Required: article_system_id.
- **List all Ongoing WMS article structure rows** (List). Get all structure rows for structure articles and production articles. Required: article_system_id.
- **List all Ongoing WMS article structure rows by number** (List). Get all structure rows for structure articles and production articles, by using article numbers. Required: articleKind. goodsOwnerId comes from the connected account.
- **Get single Ongoing WMS article by ID** (Get). Get an article. Required: id.
- **Update a Ongoing WMS article by ID** (Update). Update an existing article. Note that the articleSystemId refers to Ongoing WMS' internal ID for the article. Required: id, goodsOwnerId, articleNumber.
- **List all Ongoing WMS articles** (List). Get all articles which match the specified search criteria. The search criteria are specified in the query parameters. goodsOwnerId comes from the connected account. The connector pages through all results (500 per page).
- **Create a Ongoing WMS article** (Create). Create or update an article by its article number. Required: goodsOwnerId, articleNumber.
- **Ongoing WMS articles search** (Search). Search articles with a query body. Required: goodsOwnerId.
- **List all Ongoing WMS goods owners** (List). List goods owners.
- **Get single Ongoing WMS goods owner by ID** (Get). Get goods owners. Required: id.
- **List all Ongoing WMS historical inventories** (List). Get the historical stock balances for all articles at a specific time in the past. Required: stockDate. goodsOwnerId comes from the connected account.
- **Ongoing WMS inventory adjustment articles confirm** (Action). Mark an article of an inventory adjustment as reported. Required: inventory_id, article_system_id.
- **Get single Ongoing WMS inventory adjustment by ID** (Get). Get a specific inventory adjustment. Required: id.
- **List all Ongoing WMS inventory adjustments** (List). Get all inventory adjustments which match the specified search criteria. goodsOwnerId comes from the connected account.
- **List all Ongoing WMS invoices** (List). Get all invoices which match the specified search criteria. This function requires an additional permission for the API user, see Administration-&gt;Integration-&gt;API for goods owners. goodsOwnerId comes from the connected account. The connector pages through all results (500 per page).
- **Get single Ongoing WMS invoice by ID** (Get). Get an invoice. This function requires an additional permission for the API user, see Administration-&gt;Integration-&gt;API for goods owners. Required: id.
- **List all Ongoing WMS location types** (List). Get all location types.
- **List all Ongoing WMS movements** (List). Get physical warehouse movements. Required: moveTimeFrom. goodsOwnerId comes from the connected account.
- **Ongoing WMS order class assignments bulk delete** (Delete). Remove the order classes of an order. Required: order_id.
- **Create a Ongoing WMS order class assignment** (Create). Set (replace) the order classes of an order. Required: order_id.
- **Ongoing WMS order class assignments attach** (Action). Add order classes to an order. Required: order_id.
- **List all Ongoing WMS order classes** (List). Get all order classes. goodsOwnerId comes from the connected account.
- **Create a Ongoing WMS order consignee and order notification** (Create). Update the consignee and notifications of an existing order. Required: order_id.
- **Create a Ongoing WMS order delivery date** (Create). Update the delivery date of an existing order. Required: order_id, deliveryDate.
- **List all Ongoing WMS order files** (List). Get all files which are attached to a specific order. Required: order_id.
- ...and 107 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
