SkuVault MCP connector
The SkuVault connector brings your products, kits, lots and warehouse stock levels into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask about inventory and update product records in plain language.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect SkuVault to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SkuVault once
-
Open Connections, choose Add connection, and pick SkuVault.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a SkuVault API key. One person generates a token in SkuVault and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
SkuVault 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.
SkuVault 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 today. The plugin directory lives at chatgpt.com/plugins.
SkuVault 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.
Connect SkuVault 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.
Use cases
What teams do with SkuVault through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Warehouse
Check stock by warehouse before promising a ship date
Ask how many units of a SKU are on hand and available in each SkuVault warehouse, and which bin locations hold them, before telling a customer when an order can go out.
-
Operations
Find low or empty stock across locations
Pull available quantities for a brand or classification and get a list of SKUs that are running down, so reorders happen before a listing goes dark.
-
Ecommerce
Add a new product without opening SkuVault
Describe the SKU, brand, classification and description in a chat and have the product created in SkuVault, then fix a typo in the title or update a cost the same way.
-
Purchasing
Log incoming lots as they arrive
Record a new lot for a received shipment and see which lots sit in which locations, so expiry and batch questions can be answered in seconds.
-
Operations
Keep external warehouse counts current
Push updated quantities for a 3PL or overflow warehouse into SkuVault in one go instead of editing counts line by line.
-
Customer service
Answer a bundle availability question on the spot
Ask how many of a kit can be built from the components in stock, and see which kits exist, while the customer is still on the line.
Try asking
- “What are the current available quantities for warehouse East?”
- “Which SKUs are low across all external warehouses this week?”
- “List inventory lots by location for our main warehouse.”
Compare
Elaichi vs Zapier MCP vs Composio for SkuVault
All three can connect SkuVault 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 SkuVault tools | Allow or restrict single SkuVault 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 SkuVault 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 | $15 per user per month. | 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.
AI tools
SkuVault tools for your AI agents
55 tools are ready to call through Elaichi's MCP endpoint the moment you connect SkuVault, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting SkuVault gets you
6 screens from the product, each doing one job for your SkuVault account.
The agent
Ask SkuVault about stock in plain language.
Get answers on inventory, warehouses and quantities straight from live SkuVault records.
- inventory items
- warehouses
- locations
- lots
Ask Elaichi to work across your apps.
What are the current available quantities for warehouse East?
Which SKUs are low across all external warehouses this week?
List inventory lots by location for our main warehouse.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One SkuVault endpoint, any MCP client.
Claude, ChatGPT and Cursor connect through one governed endpoint, no SDK or shared key.
Copy the endpoint
Tool catalog
55 SkuVault tools, ready to call.
Every inventory, warehouse and location method cataloged with no custom code required.
- Create a SkuVault token
- List all SkuVault inventory item quantities
- List all SkuVault inventory available quantities
- List all SkuVault inventory kit quantities
Toolboxes
Every team gets its own SkuVault toolbox.
Warehouse, purchasing and support teams each work from a toolbox scoped to their job.
- Warehouse Ops
- Purchasing
- Fulfillment
- Support
Shared connections
Delegated SkuVault access, no shared logins.
See who connected each account and how many teams and members share it.
- Main Warehouse
- East Region
- West Region
- 3PL Partners
Audit log
Every SkuVault call, logged and attributable.
See who did what, when, and against which resource in SkuVault.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts real work in SkuVault.
Records are fetched, grouped, drafted into a digest, approved, then posted back to SkuVault.
SkuVault digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch inventory items
SkuVault
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 Michael Brennan
Approve Deny -
Post the digest
SkuVault
Queued
Collections and dashboards
SkuVault health, computed, not asked for.
Four metrics and a 14 day chart of records created, refreshed on a schedule.
SkuVault health
Refreshed 4 minutes ago · every 15 minutes · from the inventory items collection
Inventory items
1,284 ↓ 12%
Warehouses
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Inventory items created
Last 14 days
By team
Share of activity
Main Warehouse 34%
East Region 27%
West Region 21%
3PL Partners 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect SkuVault to Claude?
First connect SkuVault in Elaichi, which asks you for a SkuVault API key and nothing else. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the address. There is no OAuth application to register in SkuVault and no client ID or secret to generate, so the whole thing takes a few minutes.
Does SkuVault work with ChatGPT and Cursor as well as Claude?
Yes. Once SkuVault is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect SkuVault once and every client picks it up.
What can an AI agent actually do with my SkuVault data?
It can look up on-hand and available quantities for any SKU, break them down by warehouse and by location, check how many of a kit you can build, and list the lots sitting in a location. It can also create and update products, create kits and lots, and push quantity updates to your external warehouses in SkuVault. Short, concrete asks like "available stock for SKU 4412 in the Reno warehouse" get better results than long paragraphs.
Does connecting SkuVault give the AI access to every warehouse and product?
The AI only sees what the SkuVault account behind the connection can see, so if that account covers all warehouses, so does the connection. Elaichi can then narrow that further, for example to read-only stock lookups for one team, but it can never grant more than the SkuVault account itself allows.
Can I stop an agent from deleting or changing things in SkuVault?
Yes. In Elaichi you can allow or block each SkuVault action separately, for example allowing stock and product lookups while blocking product updates and quantity changes. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a SkuVault connection when someone leaves?
Offboarding that person in Elaichi ends their access to SkuVault through every client at once, with nothing to revoke inside SkuVault itself. If they were using a shared SkuVault connection, it keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting SkuVault once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the SkuVault MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. SkuVault 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, 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 SkuVault?
Yes. Both let Claude, ChatGPT or Cursor use SkuVault. 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 SkuVault call.
How is Elaichi different from Composio for SkuVault?
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 SkuVault: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put SkuVault in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.