Connecting Claude to Linnworks: a self-hosted route for US-based sellers

Linnworks isn’t only a British habit — US operations run on it too, and US teams tend to arrive at the AI question early: how do we get Claude answering questions about our own warehouse data?

The build-it culture meets the buy-it math

American dev teams default to building. And an MCP server over the Linnworks API is a buildable thing: token auth with session caching, a rate-limit-aware client, MCP tool definitions over HTTP. But it’s two to three weeks of engineering time — real money at US rates — to arrive at something that already exists as purchasable source. The buy-vs-build math is not subtle when the source costs less than a single day of a contractor’s time.

Why self-host rather than SaaS it

Control and cost. The connector runs in your own Cloudflare account — no vendor between Claude and your order data, no per-seat subscription accruing forever, and free-tier Workers pricing at typical query volumes. Your team can read every line, extend the tools, and deploy variants for staging and production. It’s infrastructure you own, not a service you rent.

What you get on day one

Read-only MCP tools across orders, stock, purchase orders, returns and customers, ready for Claude Desktop, Cursor or Windsurf. The source is the exact TypeScript codebase we run in production — a one-time purchase with twelve months of updates and unlimited client deployments. Find out more →

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