MCP in architecture: protocol, uses and limits
MCP architecture: understand the protocol's role, permissions and testing before linking an assistant to business software.
By Pablo Nastar
MCP in architecture attracts because it promises to connect an assistant to Revit, Rhino, Archicad or other tools. The protocol, however, makes neither the model omniscient nor the software autonomous. It provides a structured way to expose resources and actions. Security depends on what is exposed, to whom and with which validations.
The simple rule to remember: connecting is not delegating. Before the first attempt, the team must distinguish reading, suggestion, modification and irreversible execution.
Contents
We clarify the role of MCP, then the choice of a use case, the permissions, the acceptance testing, the skills to train and the reasons not to add this layer.
What the protocol actually brings
MCP standardises the communication between a client application and a server that exposes capabilities. It can avoid a different integration for every pair of tools, but does not, on its own, define the business rules nor the quality of the actions.
The Model Context Protocol specification of 28 July 2026 describes the architecture and the primitives of the protocol. A server can expose resources, tools or prompts depending on its implementation. The presence of a public server proves neither its security nor its suitability for a professional project.
| Layer | Role | Control question |
|---|---|---|
| Client | carries the interaction with the model | which user and which account? |
| MCP server | exposes capabilities | who developed and maintains it? |
| Business software | holds the project and executes | which actions are possible? |
| Validation | authorises or refuses | who reviews before modification? |
A clear diagram helps locate the responsibilities. If the client can call a write tool, the authorisation must be visible and limited. If the server only reads metadata, the risk is different.
Start from a narrow use case
An MCP pilot must start from an observable and reversible task. « Pilot the project with AI » is too broad. « List the views that do not follow a naming convention » lets you define an input, an output and a check.
Reading before writing
Start by querying a test model: properties, lists, inconsistencies or selected elements. Ask for a structured output and compare it to the software. A reading error must be understood before authorising the slightest modification.
Limited writing
A write action must announce its scope, present a preview and offer a rollback. Generic commands that can modify the whole model require a higher level of control. Work on a copy and keep the log of the actions.
Hypothetical implementation. An assistant could ask the MCP server for the list of views in a demonstration file, propose names compliant with a convention, then wait for an explicit selection before any modification. This mechanism is a pilot example, not a deployment carried out at an Educasium client.
Permissions, provenance and maintenance
The critical point is not only what the assistant understands, but what the server authorises it to do. A component downloaded from a repository must be examined like code that acts in the business environment.
Identify the author, the licence, the frequency of updates, the dependencies and the network access. Check the behaviour when the software, the API or the model changes. An old demo may work on a specific version and fail elsewhere.
The ANSSI publishes security recommendations for generative AI systems. They help place the connector within a larger system: identity, secrets, logging, compartmentalisation and monitoring.
Educasium already publishes MCP resource sheets. This article does not replace them; it provides the common method that must precede trying an MCP for architects resource.
Test quality without confusing fluency and accuracy
An assistant can describe a plausible action that no tool actually executes. The test must compare the stated intention, the call sent, the result in the software and the record kept.
Prepare normal cases and edge cases: missing object, empty selection, different unit, locked file and repeated action. Check that the server cleanly refuses what exceeds its scope. An explicit error is preferable to a silent partial modification.
Our guide on AI tools for architects helps place MCP among the other families of tools. The comparison of architecture AI software covers the functional choice; here, the subject is integration and responsibility.
Train the roles, not only the end user
An MCP pilot concerns, at minimum, the business user, the person who maintains the server and the person responsible for the data. Training only the person who writes the queries leaves the access and the updates without an owner.
The training programme must explain the boundary between a natural-language request and a technical action. It must also teach how to read a log, suspend a connector and report an unexpected behaviour. The guide to AI training in companies provides a basis for distributing these levels.
Delimited experience and Educasium's position
Educasium documents and trains in AI uses for the architecture trades; we do not claim to have deployed the cited servers in a client project. Our view is that learning must start from a sandbox model and a read permission. The value of a connection does not justify skipping the acceptance testing.
This educational choice avoids turning a demonstration into a production promise. It also allows several implementations to be compared with the same criteria: scope, traceability, recovery and maintenance.
Limits and counter-cases
MCP is not necessary for every task. Exporting a table, using an official API or writing a controlled script can be simpler and more stable. The protocol adds a layer that must be maintained.
Avoid a pilot if the project has no test copy, if the rights are not understood or if no one can examine the server. Do not connect a sensitive model to save a few minutes on a rare task. The benefit must offset the added technical and organisational surface.
Frequently asked questions
Is MCP an artificial intelligence model?
No. It is an exchange protocol between a client application and servers that expose capabilities. The model can use these capabilities depending on the client and the authorisations. The quality of the model and the security of the server remain distinct subjects. Each layer must be evaluated.
Can an MCP server modify a model file?
Yes, if its implementation exposes write actions and if the software allows them. This is not automatic for all servers. Check the declared tools, the code and the permissions. Start on a copy with preview and human validation.
Can a server found on GitHub be used?
It can be studied, but it must not be run in production on the sole faith of its page. Examine the author, the licence, the dependencies, the secrets and the network access. Have the code reviewed if the risk justifies it. Then test in an isolated environment.
Which skill should be taught first?
Breaking down the use case and reading the permissions come before the art of the prompt. The user must know what the tool can read and modify. They must also recognise an action that exceeds the request. This understanding stays useful even if the implementation changes.
Preparing a responsible MCP pilot
Training eligible for OPCO/FIF PL funding subject to conditions. Qualiopi-certified organisation. Discover the AI training for architects or contact Educasium to scope a learning environment without sensitive project data.