What MCP actually unlocks for a Linnworks operation

The Model Context Protocol sounds like plumbing because it is plumbing. What matters is what flows through it: your live Linnworks data, answering plain-English questions.

Before and after

Before: "which SKUs dropped below reorder point this week?" means someone exports a CSV, filters it, and reports back tomorrow. After: you ask Claude, the MCP server translates the question into Linnworks API calls, and the answer arrives in seconds — live data, no export, no waiting on whoever owns the spreadsheet.

What a Linnworks MCP server exposes

Well-designed tools over the API: search open and processed orders, stock items and levels, customers, purchase orders, returns and refunds. The AI chooses which tools answer the question; the server enforces what is allowed — read-only scopes mean the assistant can look but never despatch, cancel or edit.

Who this is for

Ops managers who live in ad-hoc questions, and the developers who serve them. If you are the developer, you can build the server yourself — or start from production-tested source. Ours is £249, deploys to your own Cloudflare account, and is the exact code we run against our own warehouse.

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