What is MCP? (And why L&D and HR leaders need to pay attention)
The four-minute MCP explainer your developer colleagues couldn't give you.
What is MCP?
You may have heard this term at a conference, Googled it, and still ended up confused. The first thing to get out of the way is that MCP is a standard – much like the plug socket on a wall. You don’t necessarily think about the wiring behind it; you just plug your devices in and go.
But if you’re in L&D or HR right now, MCP is probably the most important acronym you’re not yet fluent in. That’s all about to change.
What does MCP actually stand for?
MCP stands for Model Context Protocol. It’s an open standard created by Anthropic (the company behind Claude AI) and it’s been adopted by pretty much every major AI company since. Here’s what it does, in plain English: It’s a rulebook that lets AI assistants talk to the software your organisation already runs on. That includes:
- Your HRIS
- Your LMS
- Your calendar
- Your CRM
- Your content library
…and everything in between.
"MCP is the protocol that turns your AI assistant from a very smart chatbot into something that can actually do things inside the systems your organisation runs on."
Before MCP existed, every company building AI tools had to invent their own way of connecting AI to other software. Custom integrations. One-off builds. Expensive, slow, and messy. MCP changes that by making the connection standard — so any AI that speaks MCP can talk to any system that supports it.
Why does this matter for HR and L&D?
Think about what you actually do every day. You’re juggling learner data, content libraries, skills frameworks, onboarding workflows, performance reviews, and about twenty-five different browser tabs. The challenge for you has never been a lack of data; rather, getting the information to the right person at the right moment – without everything becoming a full-time admin job.
That’s exactly what AI, connected via MCP, aims to solve.
Today, your AI tools mostly live in their own lane. You might use an LLM to draft an email. You might use your LMS separately. You might pull a skills report from a third tool. Everything works in isolation.
But with MCP, the walls between those tools start to come down. Your AI assistant can see what your learners are actually completing. It can check your HRIS to see what roles are changing. It can surface the right content at the right moment, inside the flow of work — not as a separate task to go and find.
A concrete example of MCP in action
Let’s say a new manager joins your organisation. Without MCP-connected tools, getting them up to speed is a lengthy, manual process. Someone sends them a Confluence page, someone else adds them to a Slack channel, your L&D team manually assigns a few courses and hopes for the best.
With AI connected via MCP, that friction is removed. The moment that new manager is added to your HRIS, everything else can follow automatically. The right onboarding pathway appears in the LMS. Their calendar gets blocked for a ‘Manager Essentials’ session. Their team gets a heads-up. And if they have a question at 11pm on a Sunday, the AI can answer it from the context of their actual role instead of a generic knowledge base article.
This is just the start of what MCP can make possible.
How MCP went from new release to industry default overnight
MCP was released publicly at the end of 2024. In AI years, that's ancient history — but by human standards, it just happened. And yet in that short window, every major AI company signed up.
When the whole industry moves that fast in the same direction, it tends to mean one thing: This is where everything’s heading.
For L&D and HR leaders, the timing matters. The organisations that understand what MCP enables, and start asking the right questions of their technology vendors, will be well ahead of those who catch up later.
Worth knowing: MCP doesn’t replace your existing tools. It’s the layer that allows them to talk to each other through AI. Think of it less as a new platform, and more as the connective tissue your tech stack has been missing.
What does this mean in practice for your tech choices?
When you're evaluating any AI-powered learning or HR tool from here on, MCP support is worth adding to your checklist.
Ask:
- Does this platform support MCP?
- Can it connect to the other tools in our stack?
- Can the AI act on information across systems — or does it only know what's inside its own walls?
The platforms that support open standards like MCP are the ones being built for where work is heading, not where it's been.
From understanding MCP to acting on it
MCP is the open standard that makes AI useful inside the systems your organisation actually runs on. It’s why your AI assistant can go from answering questions to doing things: Surfacing the right content, triggering the right workflows, and joining the dots between your tools.
You don't need to become a developer to get value from this. But you do need to know what questions to ask. And now you do.
Thrive supports MCP — which means your learning platform can work with the AI tools your people already use, inside the flow of work.
There's a distinction worth knowing before you start those conversations with your vendors. AI-enabled means the platform uses AI. AI-interoperable means your organisation's AI can use the platform. Those aren't the same thing — and in 2026, only one of them actually matters. Thrive is built for the second one.
Want to hear it straight from Thrive's Chief Product and Technology Officer? Frankie Woodhead spoke to Learning News the week this standard started changing how enterprise AI gets built. Watch it here.
This is the first in Thrive's MCP series for L&D and HR leaders. Next up: why your learning platform is probably the most disconnected tool in your AI stack — and what that's costing you.