Digital waste tracking is now mandatory for receiversThe guide

Query ’s loads from any LLM.

LoadSnap runs a Model Context Protocol (MCP) server, so you can ask about your business from inside Claude, ChatGPT and other LLMs — 'what did we move for Carter Construction last quarter?', 'who owes us money?', 'is anything out of MOT?'. You can add things too: a new customer, a vehicle, a driver, a collection request. The assistant works through purpose-built tools, scoped to your organisation, and asks you before it writes anything.

Start for free See Copilot in-app
Add MCP server
LoadSnap
Waste movements, receipts & compliance
Connected
Server URL
app.loadsnap.co.uk/api/mcp
find_movementsfind_jobscreate_customer+18 more

What it does

Your whole operation, one MCP server away.

Org-scoped tools over the records you already keep in LoadSnap, exposed over MCP so any compatible assistant — Claude, ChatGPT and others — can look them up on your behalf.

Movements and receipts

Transfer notes, receiving receipts, loads and tonnage, and what is still to file with DEFRA.

The diary

Jobs booked in, in progress or done, by customer and date — and what is still unallocated.

Invoices and money owed

What is outstanding, what is overdue and who it is with, totalled across every unpaid invoice.

Fleet and team

Vehicles with their MOT, tax and insurance dates, and who on the team holds which app.

Compliance and paperwork

Certificates and permits with their expiry, stored documents, contracts and quarterly returns.

Adding records, safely

Add a customer, site, carrier, vehicle, driver or collection request by describing it. Missing something? It saves nothing and asks.

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.

  • 5. Or tell it to add something

    'Add Carter Construction as a customer, 12 Mill Lane, M1 1AD.' It asks you to approve, then it is in LoadSnap.

  • Full reference

    Endpoint, authentication and all 21 tools are set out in the connector documentation.

Read the connector docs
Claude
What did we move for Carter Construction last quarter?
find_movements· LoadSnap
7 movements for Carter Construction Ltd between April and June — mostly mixed C&D (17 09 04), plus one load of iron and steel (17 04 05) on 12 June.

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. Every query is scoped to your organisation, the handful of tools that add a record cannot edit or remove one, and the same searches are available inside the app through Copilot.

  • 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.

  • 15 tools read, 6 add

    The ones that add are marked as such, so your assistant asks you first. Nothing edits or deletes, files to DEFRA, signs a transfer note, raises an invoice or hands out an office login.

  • Never a half-filled record

    A request missing something required writes nothing and tells you what is still needed. Ask twice and you get the record you already have back, not a duplicate.

Connection details
Authorised asYour LoadSnap login
ScopeYour organisation only
Access15 read · 6 add
PlanPro and above

Questions

MCP connector questions, answered.

01What is MCP?
The Model Context Protocol is an open standard for connecting AI assistants to external systems. An MCP server describes a set of tools an assistant is allowed to call; LoadSnap's server exposes 21 tools over your own records - 15 that look things up and 6 that add one - using the standard Streamable HTTP transport.
02Which assistants work with the LoadSnap connector?
Any MCP-compatible client. Claude and ChatGPT both support remote MCP connectors today - you add LoadSnap once, then ask about your movements, receipts and carriers inside a normal conversation.
03Can the assistant change my records?
It can add 6 kinds of record - a customer, a receiving site, a carrier or broker, a vehicle, a driver and a collection request - and your assistant asks you before it does. Nothing else. No tool edits or deletes anything, files to DEFRA, signs a transfer note, raises an invoice or gives anybody an office login, so the worst a misfired prompt can do is add a record you can change or archive in LoadSnap.
04What happens if it doesn't have everything it needs to add something?
It saves nothing and tells you what is still missing, in plain questions - 'what is the postcode?' - so you answer and it tries again. You never end up with a half-filled record. Ask for something that is already in LoadSnap and it hands you the record you have rather than making a second.
05Can I use this instead of a spreadsheet import?
For getting a handful of things in, yes - describe them and your assistant adds them. For a few hundred rows off an old system, the CSV import in Settings is still the quicker route, and the two write to exactly the same records.
06What can it actually look up?
Movements and receipts, loads and tonnage, DEFRA filings, the jobs in the diary, invoices and what is still owed, vehicles and their MOT and tax dates, who is on the team and which apps they hold, certificates and permits with their expiry, stored documents, skips and containers, contracts and season tickets, quarterly consignee returns, and the national waste code list.
07Who can connect, and what do they see?
Anyone with a LoadSnap login on a Pro plan or above. Each connection is authorised as that person and every query is hard-filtered to their organisation, with membership re-checked on every request - remove someone from your organisation and their connector stops working with it.

Digital waste tracking is live

The mandate is here.
Automate compliance.

Receiving sites in England and Wales have had to record every load digitally since 1 October 2026. Start a 14-day free trial in minutes, cancel any time before it ends, and file every load from day one.

Start for free Book a demo

DEFRA API integrated · EA carrier verification · UK data residency