The Hosted MCP Server for Linnworks will let you connect Claude to your own Linnworks account and ask about it in plain English: which orders are stuck, what is running low, which refunds need action, where a purchase order has got to. We run the server, so there is nothing to deploy and no API keys to paste, and if you want Claude to change something it shows you exactly what will happen and waits for your yes. It is coming very soon. This post explains what it will do, how connecting works, how your data is handled, and how to get on the waiting list.
What is an MCP server, briefly?
MCP, the Model Context Protocol, is an open standard that lets an AI assistant use tools: look things up in another system, and act on them when allowed. On its own, Claude knows nothing about your business. Add an MCP server for Linnworks and Claude can call a defined set of Linnworks tools, so its answers come from your live account rather than from guesswork. You stay in the conversation; the server is simply the bridge.
We already sell the Linnworks MCP source code for teams who want to run that bridge on their own Cloudflare account. The hosted server is for everyone who would rather not: we run it, you connect.
What you will be able to ask
The hosted server reads your Linnworks account live, each time you ask. It covers four areas:
- Orders. Search the open order book (orders not yet despatched) by source, sub-source, location or keyword, search processed orders over a date range for sales analysis, and pull the full record of any order: line items, addresses, totals and channel.
- Stock. Search your catalogue by SKU, title or barcode, and get per-location stock levels for any item.
- Purchase orders. List and search supplier purchase orders by status, supplier, date range or reference, and open any PO with its items and deliveries.
- Returns and refunds. Search returns or refunds history between two dates, see every refund on a processed order, and list the refunds still waiting for action.
In practice that means questions like these, asked the way you would ask a colleague:
- "Which open orders have been waiting more than two days?"
- "What is the stock of this SKU at each location?"
- "Which purchase orders from this supplier are still open?"
- "Give me this morning's list of refunds that need action."
Because Claude can combine several lookups in one answer, the useful questions are often the ones that would normally mean three screens and a spreadsheet. If you run the same Monday reports by hand every week, our post on reports your ops manager can stop running is a good list of starting points.
Changes you approve, one at a time
Reading is half the job. On the plan that includes changes, Claude will also be able to:
- update the base retail price on up to 50 stock items at a time (channel-specific listing prices are left alone, and a change of more than 50% either way is refused unless you explicitly allow it);
- archive up to 100 items, refusing any that still hold stock, are committed to an open order or are due on a purchase order, and restore archived items;
- create one new open order of up to 50 lines, with every stock item checked live first.
None of these happens in one step. Every change is a preview, then confirm pair. Claude first reads the live data and shows you exactly what will change, before and after. Only when you say yes does it call the confirm step, and each confirmation works once and expires after ten minutes. Every change made this way is written to an audit log, and your most recent changes are listed in your account. It is the same rule we apply to our own AI agents at Green & Home: an assistant can prepare a change, but a person decides.
How connecting will work
- Sign in with your email. There is no password; you get a six-digit code by email.
- Connect Linnworks. Press the button and approve the app inside Linnworks. Linnworks issues a token for your account, so you never share your Linnworks password or API keys with us.
- Add it to Claude. In Claude, open Settings, then Connectors, choose Add custom connector, paste your server URL and press Connect.
- Approve access and start asking. Claude signs in to the server with OAuth, you approve it once, and you can ask your first question straight away.
The server is built on the open MCP standard, so other assistants that support remote MCP servers with OAuth sign-in should be able to connect in the same way. Claude is the one we use every day.
How your data is handled
- Nothing copied. Your orders, customers and stock are never stored by the server. Everything is read live from Linnworks when you ask.
- Encrypted token. The token Linnworks issues for your account is encrypted at rest (AES-256-GCM) and kept out of logs and error messages.
- Your account only. Each account can only ever reach its own Linnworks data.
- A short audit trail. Changes made through your assistant are logged for 90 days so you can see what was done and when.
What Claude does with the answers it receives is governed by your own Claude account and its settings, so it is worth checking those as you would for any other connector.
Who it is for
Linnworks sellers who already use Claude and want quicker answers from their own account without building anything. If you would rather run everything on your own infrastructure, the self-host source code is still the route for you. If your problem is order entry rather than answers, look at Trade Order POS.
Pricing and launch
Pricing: Starter is £13.99 a month inc VAT; Pro is coming soon. It opens very soon. Prices on mcp-g.com are shown in GBP.
The Hosted MCP Server for Linnworks is an independent product of Green & Home Limited (trading as MCP-G). It is not affiliated with, endorsed by or sponsored by Linnworks Ltd or Anthropic; their names are used only to describe what it works with.
Want to be first in? Join the waiting list below and we will email you when it opens. More detail is on the Hosted MCP Server for Linnworks page.