JUNE V10 · Model Context Protocol
The best of both worlds: the intelligence of your assistant, the case knowledge of JUNE.
International law firms and companies trust JUNE
JUNE MCP
In law firms and legal departments, the AI assistant has become the first screen of the day. Its usefulness depends on what it can access. JUNE MCP connects the assistant to the full case portfolio, so teams can work directly with their matters, deadlines and documents in Copilot, Claude or ChatGPT.
And again, for the next matter
JUNE V10 · Video
In practice
The direction is what matters. Most connections of this kind only read: they search document sets, summarise, report back. JUNE MCP writes back. The work ends at a result that is already part of the matter, rather than at an answer in a chat window that somebody then transfers by hand.
Asking
Writing back
Providers
The tool your organisation standardises on this year has a successor next year. Until now that meant a migration project. Now it is a setting.
ChatGPT Available 
Claude Available 
Copilot Available 
Legora In preparation 
Harvey In preparation 
More providers Coming soon Model Context Protocol
50+ JUNE functions, reachable from Copilot, Claude and ChatGPT
Claude, Copilot and ChatGPT already know how legal work is done – drafting, researching, structuring an argument. What they don’t have is the matter itself: which client, which deadline, which document is on file. Until now, that had to be typed in or copied over by hand, one case at a time.
The server isn’t rebuilt for each provider – it follows the Model Context Protocol, the standard the leading AI providers have settled on. Connect once, and more than 50 functions reach the same case files, deadlines and documents across Copilot, Claude and ChatGPT. The tools will keep changing. The file stays.
Your teams work in the assistant they already have open. Switching it later costs a configuration change, not an integration project.
Permissions & security
Nobody gets new permissions. Everyone keeps the rights they already have.
JUNE V10
Four further changes ship with the release. They concern the work inside the matter itself, where the tasks originate that the assistant then drives from the outside. Each of them gets its own page over the coming weeks.
Several claim accounts per matter, with claims, interest, costs and payments in one view. Base rate rules and the statutory order of payment allocation (§ 367 BGB) are built in, repayment schedules are generated from instalment size or term, and statements of claim export as .docx and .pdf.
Messages from Germany’s secure electronic mailboxes for legal correspondence are retrieved and sent from within the platform. They run through the configured inbound message process, so electronic filing takes the same path as the rest of the post. Use requires the corresponding licences.
We have integrated even more comprehensive tools to help you manage large volumes of files and data: change thousands of facts in a single step or run workflows across all your files.
Working with emails is now an inherent part of JUNE files. Manage the entire communication flow in the JUNE Story and automate your email correspondence with other parties.
Live demo
See how MCP enhances AI case management – walked through in a live demo environment, built to show how the real workflows run.
Connect MCP and test it live in your own JUNE environment, on your own teams and matters.
