AI over your Linnworks data: the case for UK in-house teams self-hosting

The fastest way to let Claude query your Linnworks account is someone else’s hosted connector. The most defensible way, for a UK business, is your own.

Why UK teams care where the connector runs

Your Linnworks account holds customer names, addresses and order histories — personal data under UK GDPR. Route it through a third-party hosted connector and that provider joins your data map, your due-diligence list and your risk register. Run the connector in your own Cloudflare account and there is no extra party: Claude talks to your Worker, your Worker talks to Linnworks, and the accountability stays in-house where your ICO registration already lives.

What self-hosting gets you

Read-only MCP tools over orders, stock, purchase orders, returns and customers — so anyone on the team can ask questions in plain English instead of exporting CSVs. The Workers free tier typically covers the volumes involved, and because you hold the source, your developers can adapt it as the business changes. See what MCP unlocks for Linnworks.

Build or buy the starting point

Building from the API docs is two to three weeks of competent work; the honest comparison is in buy vs build. The Linnworks MCP source is the production codebase we run against our own UK warehouse — £249 one-off, twelve months of updates, deploy to your own account and keep it. Find out more →

Questions, or want a tool we don't have yet? Email hello@grafto.co.uk — a real person replies.