Linnworks MCP for EU agencies: AI connectors your clients’ DPOs will accept

Pitch an EU client on connecting Claude to their Linnworks account and the first email back is from whoever minds their GDPR compliance. Your architecture is your answer.

The question every EU client asks

“Which parties process our customer data?” A hosted third-party connector adds a processor to the client’s records, a data-processing agreement to negotiate, and a dependency to explain. A connector deployed into infrastructure the client controls adds none of that: the MCP server runs as a Cloudflare Worker on their account, speaking directly to Linnworks. Fewer parties, shorter answers, faster sign-off. The regulation itself is the client’s counsel’s territory — official texts live at europa.eu — but architecture that minimises data hops is an easier conversation in any member state.

The agency economics

The Linnworks MCP source licence allows unlimited client deployments from a single purchase — one £249 codebase, deployed per client, each instance isolated in that client’s own Cloudflare account. Compared with building per client, or reselling a hosted service you don’t control, the margin story writes itself. The deployment mechanics are covered in self-hosting a Linnworks MCP server.

What clients get

Plain-English questions over orders, stock, purchase orders, returns and customers — read-only by design, which is itself a compliance feature: the AI can look, not touch. Find out more →

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