Richard Mabey

MCP is here. But what does this mean for the future of contracting?

AI
September 9, 2025
Most legal teams are already talking to AI, the next step is letting AI talk to your tools.

That is the promise of the Model Context Protocol, or MCP, which turns ChatGPT and other LLMs into a control panel for the systems where your contract data lives.

In practice, that means a lawyer can ask a plain language question and get a precise, cited answer from Juro without changing tabs.

From integrations to orchestration

Traditional integrations moved fields and fired notifications. Useful, but narrow. MCP is different. It lets one system instruct another and fetch the right data on demand. Think of it as a universal connector that upgrades chat into an operating layer for work. Instead of logging in to six apps, you bring the work to a single interface and keep humans in the loop where judgment matters.

Why this matters now

The market has moved. In our live session poll, 92 percent of attendees said they use AI tools in day to day work. ChatGPT led at 38 percent, followed by Gemini at 19 percent and Claude at 11 percent. Only 10 percent said they rely on a legal AI point tool. When asked about their hardest contract data challenge, 40 percent chose finding information fast, 21 percent tracking key dates, 17 percent reporting for finance and leadership, and 21 percent something else. The conclusion is clear. Lawyers are already in chat. Speed to insight is the top need.

Contracts should live where work happens

This has always been Juro’s mission. Contracts in Salesforce for sales. Contracts in Slack for intake. Contracts in Word for review. MCP extends that mission into AI interfaces. If your teams live in ChatGPT, they can now reach Juro from there. We are also building an MCP integration with Wordsmith so mutual customers can query and act on contract data inside the tools they already use.

What good looks like in practice

Senior Legal Engineer Henry Warner walked through a simple flow. Connect ChatGPT to your Juro repository with a secure toggle, no code required. Ask for the NDAs signed this quarter. See the list with links back to source documents. Ask follow up questions. Pull out smart fields where they exist. Extract key terms from the document body where they do not. Visualise timelines and owners from the same chat thread to brief a stakeholder in minutes.

You can go further. Ask for contracts with autorenewal next year. Filter by value above 100,000 dollars. Request a summary of payment terms for a named counterparty. Prompt a deep dive on assignment or change of control language across the portfolio and get a cited report, then click through to verify before acting. This means no custom report builder, no spreadsheet wrangling and one conversation that compounds.

Join the conversation

If you want to learn more about using Juro with MCP and ChatGPT, please contact your CSM. If you are new to Juro, request a demo below and see how end to end contracting and AI can work together in your stack.

Accuracy, governance and trust

Every AI conversation about contracts must address risk. Three points matter.

First, source of truth. The MCP connection fetches content from Juro directly. It uses Juro’s OCR and repository context, then passes only what is needed to the model for the question at hand. Results link back to the documents so reviewers can check before they act.

Second, data protection. Juro’s MCP configuration is set to opt out of model training. Your own ChatGPT tenant settings should also be configured to prevent training on your data. Think of this as belt and braces. The operational standard should match the rest of your stack, the same way you assess Salesforce or Slack.

Third, access control. ChatGPT sees only what the requesting Juro user can see. Rights map through the connection. If a sales user does not have permission for a sensitive agreement inside Juro, they will not surface it in chat either.

There is still model risk. LLMs are powerful, not perfect. That is why citation, human review, and fit for purpose workflows remain essential. For high stakes reporting, smart fields and AI Extract inside Juro can produce the structured outputs you need. For discovery and decision support, natural language questions in chat deliver speed.

A new interface for legal work

MCP doesn't replace search. It reframes it, search becomes conversation, the interface becomes the process and that unlocks three key shifts.

  1. Self serve at scale. Sales or People teams can request a draft, check a clause, or confirm a renewal date from a chat interface they already use. Legal defines the guardrails, and the system enforces permissions.
  2. Faster analysis. Instead of exporting to sheets, users can ask for a visual and iterate. Which agreements are most likely to trigger a notice this quarter. Who owns each renewal and when to start outreach. What risk themes recur in a target set for diligence. Answers arrive with links, not lore.
  3. No code automation. MCP lowers the integration lift across tools. Today we showed ChatGPT. Tomorrow the same pattern can extend across the AI tools your company prefers, with the same security posture and governance.

What legal leaders should do next

Treat MCP as an opportunity to redesign the path from question to answer. Start with the moments that generate the most context switching, delays, and back and forth. Typical candidates include renewal sweeps, board reporting, M&A readiness, and policy compliance checks.

Define the level of assurance you need for each use case. Discovery and triage can live in chat. Final numbers for an audit should come from structured fields. Make it explicit which workflows are exploratory and which are definitive.

Tighten the feedback loop. Require citation to the source document for any analytic output. Keep role based access controls current. Review tenant settings for model training and retention. Set prompts and exemplars for common requests so your teams start strong without a PhD in prompting.

Invest in enablement. The most successful teams pair a legal engineer or ops lead with champions in Sales, Finance and HR. Short sessions. Real data. One or two valuable questions per function. Adoption follows value.

About the author

Richard Mabey
CEO and co-founder of Juro

Richard Mabey is the CEO and co-founder of Juro, the intelligent contract automation platform. Under his leadership, Juro has scaled rapidly, backed by $38 million in venture funding from prominent investors including Eight Roads, USV, Point Nine Capital and Seedcamp, and the founders of companies like Indeed, Gumtree and Wise.

Richard trained and qualified at Freshfields Bruckhaus Deringer, working as an M&A associate in London and New York. He gained an MBA from INSEAD, and then spent time at LegalZoom, learning to build legal tech products.

Frustrated by the manual legal processes that slow down businesses, Richard co-founded Juro in 2016, with a mission to help the world agree contracts faster. Beyond Juro, he hosts the "Brief Encounters" podcast, makes angel investments, and supports other ambitious ventures from the boardroom. Richard is a Fellow of the RSA, an adviser to The Entrepreneurs Network and sits as a Non-executive Director of Bright Blue.

Instantly book a personalized demo

  • Schedule a live, interactive demo with a Juro specialist

  • See in-depth analysis of your contract process - and tailored solutions

  • Find out what all-in-one contract automation can do for your business

Schedule a demo

To learn more about the use of your personal data, please consult our readable Privacy Policy.

Your privacy at a glance

Hello. We are Juro Online Limited (known by humans as Juro). Here's a summary of how we protect your data and respect your privacy.

Read the full policy
(no legalese, we promise)