Ask Claude, Copilot, ChatGPT or Grok what is due this week, pull a pupil passport before covering a class, or work through a provision map — without leaving the tool you are already in. No new app to learn, and no copying between systems.
https://agw.weaveone.co.uk/sconnect-mcp/mcp
This is the question schools ask first, so here it is plainly.
Your assistant sees a stable reference such as MA-050f with year group and primary need — enough to work with, and enough for you to recognise the child. Real names are only shared if your data-protection lead asks us to enable it, per school, and that can be turned off again at any time.
Safeguarding and medical can be unlocked read-only by explicit request with your DSL's agreement — they are off unless you ask, and even then the safeguarding narrative itself is withheld.
One deliberate exception: allergies and dietary needs are available, including severity and whether an EpiPen is needed. A teacher needs that before a cooking lesson or a trip, and withholding it would be the more dangerous choice. So is the fact that a care plan was reviewed — but not the plan itself.
Every tool here is a database query — your assistant does the thinking, we supply the data. Nothing in this connection calls a model on our side, so it does not touch your SendConnect360 AI allowance no matter how much you use it.
There is no tool that emails or messages anyone. An assistant can read a parent's message and draft a reply for you, but it cannot send it, and it cannot submit anything to the local authority. This is deliberate: an assistant that reads text written by outsiders should not also have a way to send data back out to them.
If you work at more than one school you choose which school a connection is for when you authorise it. It cannot reach the others, and your role at that school decides which tools appear — a teacher does not get SENCO tools.
Every request is logged — who asked, which tool, which school, when. Revoke a connection in Settings and it stops working immediately.
Most assistants sign you in themselves: they open a browser, we email you a one-time sign-in code, and you pick the school and confirm what the assistant may do. Nothing is shared until you approve that screen.
The code only needs your school email, so it works whether you normally sign in with a password, a magic link or Google. Assistants that cannot do this yet — Copilot and Grok — use an access token you generate in SendConnect360 instead.
Nothing technical here: you paste one address, sign in with your school email, and you are done. If any of this feels unfamiliar, forward this page to whoever looks after your school's IT — it is a two-minute job for them.
Some tools cannot run the sign-in flow and use an access token instead. An access token is a long random code that stands in for signing in — think of it as a password that you create once, paste into the tool, and never type again. Generate one on the Connect AI page in SendConnect360 (Access tokens section). It is shown once — copy it straight into the config where it says YOUR_TOKEN; if you lose it, revoke it and generate a new one. Treat it exactly like a password: it grants access to pupil data, so never email it or put it in a shared document, and revoke it the moment it is no longer needed. Teachers should never need to handle one — the section above covers them.
Run this, then type /mcp and choose Authenticate.
claude mcp add --scope user --transport http sendconnect360 \ https://agw.weaveone.co.uk/sconnect-mcp/mcp
Copilot reads .vscode/mcp.json and does not run the sign-in flow, so generate an access token in SendConnect360 first (see the box above), then put it where YOUR_TOKEN is:
{
"servers": {
"sendconnect360": {
"type": "http",
"url": "https://agw.weaveone.co.uk/sconnect-mcp/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}Grok connects from the API rather than a settings screen — one for whoever builds your integration.
"mcp_servers": [{
"server_label": "sendconnect360",
"server_url": "https://agw.weaveone.co.uk/sconnect-mcp/mcp",
"authorization": "Bearer YOUR_TOKEN"
}]Copilot is different from the assistants above. Those are set up by each teacher on their own machine; Copilot is connected once for the whole school by whoever administers your Microsoft 365 tenant, and then every member of staff uses it without any setup of their own.
Your IT administrator needs a Microsoft 365 Copilot licence and access to the Microsoft 365 admin centre. Nothing needs installing, and there is nothing for WeaveONE to switch on at our end.
https://agw.weaveone.co.uk/sconnect-mcp/mcpA connection on its own is not always enough — plain Copilot chat decides for itself whether to use a connector, and often will not. The reliable route is to build an agent in Copilot Studio that lists SendConnect360 as its knowledge source, publish it, and share it with your SEND team. Staff then open a named assistant rather than hoping Copilot reaches for the right thing.
Copilot Studio needs its own licence, separate from Microsoft 365 Copilot. If your school does not have one, staff can still use Claude or ChatGPT from the section above, which need no licence beyond the assistant itself.
Exactly what the signed-in member of staff can see, and nothing more. Each person signs in themselves and picks their school, so the access is theirs — a connection made by an administrator does not give the whole school access to every pupil. Records are read live at the moment of the question and are not copied into Microsoft or indexed there.
One thing to insist on with staff: if an assistant ever asks them to paste or upload a pupil report into the chat, the answer is no. The connector reads the record directly, and pupil information should never be pasted into a chat window.
The full guide, and the button to generate a token, are inside the app.
Open the setup guideNot a customer yet? Talk to us.