← All posts
MCP for developers · 19 June 2026 · 7 min read

Self-hosting an MCP server on Cloudflare: a 90-minute guide for Linnworks integrators

If you build software on top of Linnworks for a living — or you run an in-house engineering team and you want to plug Claude into your own warehouse — building an MCP server from scratch is two to three weeks of work. We did it once for ourselves, productionised it, and now sell the source code so you don't have to. Here's what self-hosting actually looks like.

Who this is for

If you don't have someone on your team comfortable with TypeScript and the Wrangler CLI, this isn't the right product for you — you want a hosted offering instead.

What you actually get when you buy the source

The £249 Linnworks MCP source download is a zip containing:

No watermarks, no telemetry phoning home, no obfuscation. You own the source.

The 90-minute deploy, in summary

Allowing for a buyer who's never deployed a Cloudflare Worker before, here's the realistic timeline:

  1. 0–10 min: download the zip, unpack it, run npm install.
  2. 10–25 min: register a Linnworks application at developer.linnworks.net, copy the Application ID and Application Secret.
  3. 25–40 min: wrangler login, edit wrangler.toml to give the Worker a unique name, wrangler deploy.
  4. 40–55 min: wrangler secret put for the four secrets (Application ID, Application Secret, MCP bearer token, install token).
  5. 55–75 min: install the app into your Linnworks account via Settings → Apps; capture the install token from the redirect URL; set it as the fourth secret; re-deploy.
  6. 75–90 min: paste the Worker URL and bearer token into Claude Desktop's MCP config, restart Claude, ask "what's our open orders count" and watch real data come back.

If you've done a Cloudflare Worker deploy before, knock 30 minutes off. If you haven't, the User Guide on docs.mcp-g.com covers every screen.

The agency multi-client model

The licence covers unlimited end-clients. The clean pattern: one Worker per Linnworks account.

The agencies we've seen charge between £20–£60/month per client for hosting + updates + break-fix — covers infrastructure (Cloudflare's free Workers plan handles most clients comfortably at 100,000 requests/day) and pays for ongoing support time.

What you can't do with this

Be straight about it:

The total cost of ownership comparison

One-off £249 + your Cloudflare account (free for the first 100k requests/day per Worker) + your time. If you self-host, deploy costs come down to about £0/month for typical client volumes.

Compare to building this yourself: an experienced Cloudflare Workers + Linnworks developer at typical UK rates would build the equivalent in 3 weeks. £249 vs £15k+ in salaried time is the actual trade.

Try before you commit

If you want to see what the deployed product looks like before you spend £249, our own production Linnworks MCP lives at linnworks-mcp.michael-669.workers.dev — that's the same codebase running against Green & Home Ltd's real warehouse, and it's the proof that the source you'd be buying is production-tested.

If you want the source, grab it here for £249. Instant download, one-off payment, 12 months of free updates, yours forever.

Got a tricky use case — multi-tenant routing, custom tool additions, Linnworks API write operations — and want a quick architecture chat before you buy? Email hello@mcp-g.com and we'll reply the same day.

Ready to try it?

Two clicks gets you a hosted Linnworks MCP connected to Claude. Cancel anytime.

See the Linnworks MCP →