Knowledge
What is MCP?
The shared language an AI tool uses to ask a program for data. It sounds like a detail for IT — but it is the point at which it is decided whether you tie yourself to one vendor or not.
MCP in one sentence
MCP — the Model Context Protocol — is an open agreement on how an AI assistant asks a program for data. Without such an agreement, every vendor would have to build a separate integration for every tool, and each one would be a one-way street. With it you build once and are understood by everyone who speaks the same language.
You set nothing up
The server is part of easo and ships with it — you install nothing and edit no configuration file. Once your company has switched AI access on, easo registers the channel on your device itself and then shows you a receipt of what it did. A notification, not a question.
Why an open standard matters here
A convenient integration with a single AI tool would have been quicker to build. It would have tied us — and you — to that tool, which is exactly the kind of dependence this product is built against.
-
No vendor lock-in
We did not connect one particular AI tool; we speak the language it speaks. Change the tool and your QMS stays connected.
-
It runs locally
MCP has a path where the server and the tool talk on the same machine. That is why the channel needs no network connection — a cloud integration could not do this.
-
Asked, not dumped
The assistant gets no folder; it asks individual questions. Every answer arrives on its own and carries its provenance: version, release, verification result.
-
One integration, not twenty
What works for one tool today works for the next one tomorrow, without us or you retrofitting anything.
Honest limits
MCP servers are being discussed as a security topic right now, and rightly so: in many companies employees plug in servers nobody else knows about. If you check that, check it with us too. Our answers are not assurances but properties: the server runs locally and opens no connection out, the company switches it on as a signed setting, it is off by default, and in everyday use it reads released documents only.
The standard is young. The specification still moves, and we will have to move with it. That is the price of standing early on an open foundation rather than late on somebody else's.
Browser-based assistants do not work, deliberately. They would need a remote server for your content to travel through. We do not build that one — it would cancel the promise that your documents stay your documents.
MCP governs the channel, not the model. The standard settles how questions and answers travel. What an AI tool does with the answer, and where it sends it, belongs to that tool and its provider.
What this means for your QMS
Over this channel your team's AI tools answer questions from your QMS — from the released, signature-verified state, with version and release on every answer. Who switches it on, what is served and where the boundary runs is on the page about AI access.
In short
MCP is the language, not the product. It does not decide what your AI can do — it decides whether in five years you still choose freely which AI you work with. The same reasoning that puts your documents in your own git rather than on our servers.
Common questions about MCP
What does MCP stand for?
Model Context Protocol. It is an open agreement on how an AI tool asks a program for data: what is there, give me this one, find me that. Instead of every vendor building every integration separately, everyone speaks the same language.
Do I have to install or configure anything?
No. The server is part of easo and ships with it. easo registers Claude Desktop and Claude Code itself and then shows you a receipt of what it did; other tools are connected with a command easo copies out for you.
Does it work with every AI tool?
With any that speaks MCP, and that is increasingly many. Browser-based assistants are deliberately out: they would need a remote server for your content to travel through — which is precisely what we do not want to build.
Does my data go out to the internet?
Not through easo. The server and the AI tool talk to each other on your machine; the channel opens no network connection. What your AI tool then does with what it read is decided by that tool and its provider — a question for your AI tool, not for easo.
Is an MCP server a security risk?
A fair question, and one the industry is asking loudly right now — usually because employees plug in servers nobody else knows about. Ask it of us too. Our answers: the server runs locally with no connection out, the company switches it on as a signed setting, it is off by default, and in everyday use it reads released documents only.
Stay in the loop
easo is available for macOS and Windows. The newsletter tells you what comes next — new versions and new content, nothing else.