Product · MCP server
Query your loads
from any LLM.
LoadSnap runs a Model Context Protocol (MCP) server, so you can query your waste data from inside Claude, ChatGPT and other LLMs — 'what did we move for Carter Construction last quarter?'. The assistant reads your records through purpose-built, read-only tools, scoped to your organisation.
What it does
Your compliance data, one MCP server away.
The same org-scoped search that powers in-app Copilot, exposed over MCP so any compatible assistant — Claude, ChatGPT and others — can query it on your behalf.
find_movements
Look up Waste Transfer Notes and jobs by producer or carrier, over any date range.
find_receipts
Find receiving receipts by carrier or producer, with DEFRA status and weights.
find_parties
Resolve a company or site name to the carriers and sites you actually work with.
Scoped to your org
Auth resolves to your organisation; every query is hard-filtered to it. Other tenants are invisible.
Read-only by design
It can search and surface records — never create, edit or delete anything.
Standard MCP
A standards-based Streamable HTTP server. Works with Claude, ChatGPT and any MCP-compatible client.
Setup
Connected in a few minutes.
MCP — the Model Context Protocol — is an open standard for giving an AI assistant controlled access to an external system. Honestly stated: it doesn't make the assistant smarter, it just lets it look things up in your LoadSnap account instead of guessing. Setup is a URL and a sign-in; we covered what it's like to use, alongside in-app Copilot, on the blog.
1. Be on Pro or above
The connector is available on the Pro plan and above — check Settings → Billing.
2. Add the server to your assistant
In Claude (or another MCP client), add a custom connector with the server URL app.loadsnap.co.uk/api/mcp.
3. Sign in and approve
Your assistant sends you to LoadSnap to sign in and approve the connection — it's authorised as you, on your organisation.
4. Ask a real question
'What did we move for Carter Construction last quarter?' The assistant calls the LoadSnap tools and answers from your records.
Security
The access model, plainly.
Letting a chatbot near compliance records is a fair thing to be cautious about, so the boundaries are enforced by the platform rather than trusted to the model. The connector runs the same org-scoped search tools as in-app Copilot — nothing more.
Authorised as a person, not a key
Every connection resolves to a LoadSnap user, and membership is re-checked on every request — leave the organisation and access ends with you.
Hard-scoped to your organisation
The organisation is resolved server-side from the authorised user. The assistant never supplies it, so it can't ask for anyone else's data.
Read-only, three tools, no exceptions
Search movements, receipts and parties. There is no write method on the server at all.
Questions
MCP connector questions, answered.
On the DEFRA DWT Beta
The mandate is coming.
Get compliant now.
Start for free. Live in under an hour. No credit card. Build your digital audit trail today, before the deadline forces it.
DEFRA API integrated · EA carrier verification · UK data residency