Linnworks MCP connector
The Linnworks connector brings stock levels, product performance, listing templates and customer email templates to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about inventory and prepare listings inside their own Linnworks access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which products are below their low stock level today?
Working in Linnworks with Elaichi
-
Get auth get application profile by secret key by ID
-
List all Linnworks dashboards get low stock levels
-
List all Linnworks dashboards get performance table datas
How to connect Linnworks to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Linnworks 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.
Linnworks 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.
Linnworks 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.
Linnworks 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.
Linnworks 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 Linnworks 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 Linnworks through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Linnworks is logged.
-
Warehouse
Check low stock before the morning pick
Ask which products have dropped below their low stock level and where each one is held, then plan the day's replenishment before pickers start.
-
Operations
See stock by location without opening dashboards
Get inventory location figures, category breakdowns and product counts for each warehouse in one answer, ready to paste into the daily stand-up.
-
Merchandising
Find the top products this week
Pull the top products and performance details from the Linnworks dashboards, then ask which lines are gaining and which are slipping.
-
Marketplaces
Prepare a listing template for new stock
Open the listing templates for a set of inventory items, fill in the template fields and process the template so a new range is ready to go live.
-
Marketplaces
Keep channel configurators tidy
Read a configurator's description and data, save corrections, and create a new configurator when a marketplace adds a category.
-
Customer service
Send a customer email from a template
Find the right email template, draft an ad hoc or free text email for a delayed or back in stock order, and send it without leaving the chat.
Try asking
- “Which products are below their low stock level today?”
- “Show me the top selling products this week by location.”
- “Draft a back in stock email from our standard template.”
What connecting Linnworks gets you
6 screens from Elaichi, each doing one job for your Linnworks account.
Ask Elaichi to work across your apps.
Which products are below their low stock level today?
Show me the top selling products this week by location.
Draft a back in stock email from our standard template.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Linnworks which products are running low.
Type a plain question and get answers from live stock levels and performance figures.
Copy the endpoint
AI apps
One endpoint puts Linnworks in every AI client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect once over OAuth, with no SDK and no shared API key.
Tool catalog
397 Linnworks tools, ready without writing code.
Stock dashboards, top products, email templates and listing configurators, covered with no custom code.
Toolboxes
Every team gets its own Linnworks toolbox.
Warehouse sees stock levels, marketplace staff see listing templates, each scoped to its team.
Shared connections
Teammates work in Linnworks without seeing the key.
One person connects the account and shares it, nobody else handles a credential.
Audit log
Know who touched which Linnworks listing, and when.
The audit log records when, who, what happened, and the resource, and never edits.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Linnworks digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch products
Linnworks
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
Linnworks
Queued
Automations
A schedule starts the low stock digest itself.
Stock levels are fetched, grouped, drafted into a digest, approved, then posted back to Linnworks.
Linnworks health
Refreshed 4 minutes ago · every 15 minutes · from the products collection
Products
1,284 ↓ 12%
Listings
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Products created
Last 14 days
By team
Share of activity
Warehouse UK 34%
Marketplaces 27%
Customer service 21%
Merchandising 18%
Collections and dashboards
Linnworks stock health refreshes itself on a schedule.
Four metrics, a 14 day chart of listings created, and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Linnworks
All three can connect Linnworks 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 Linnworks tools | Allow or restrict single Linnworks 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 Linnworks 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.
Linnworks tools for your AI agents
397 tools are ready to call through Elaichi's MCP endpoint the moment you connect Linnworks, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 227 of 397 Linnworks tools here. Connect Linnworks and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Linnworks to Claude?
Connect Linnworks in Elaichi first: paste your Linnworks API key when prompted, and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi and Linnworks appears with everything else you have connected.
Does Linnworks work with ChatGPT and Cursor as well as Claude?
Yes. Once Linnworks 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 Linnworks once and every client picks it up.
What can an AI agent actually do with my Linnworks data?
It can tell you which products are below their low stock level, what stock sits in each location, which products are selling best and how performance looks over a period. It can also find email templates and send a customer email, and open, fill in and process listing templates and channel configurators. Linnworks has a lot of capabilities, so short, concrete asks such as "low stock in the Leeds warehouse" get better results than long paragraphs.
Does connecting Linnworks give the AI access to everything in my account?
No. Every request runs as the person who signed in, using their own Linnworks permissions, so the AI sees the locations, listings and templates that person can already see. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Linnworks itself allows.
Can I stop an agent from deleting or changing things in Linnworks?
Yes. Restrictions in Elaichi apply per action, so you can allow reading stock levels and top products while restricting anything that saves a template, changes a configurator or sends an email. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Linnworks connection when someone leaves?
Offboarding that person in Elaichi ends their access to Linnworks through every client at once. If they connected a shared Linnworks account, the connection keeps working for everyone else it was shared with. When you want Linnworks gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Linnworks MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Linnworks 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 Linnworks?
Yes. Both let Claude, ChatGPT or Cursor use Linnworks. 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 Linnworks call.
How is Elaichi different from Composio for Linnworks?
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 Linnworks: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Linnworks 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