MCP Archicad: preparing rights and tests
MCP Archicad: check versions, permissions, a test model and acceptance before connecting an assistant to the agency BIM flow.
By Pablo Nastar
An Archicad MCP can connect an assistant to information or commands exposed by an implementation. The promise seems simple; the BIM context is not. Software version, shared work, editing rights, classification and project conventions determine what can be tested without endangering the model.
The right first question is not "what can the assistant do?", but "what project state are we willing to show it, and what action are we willing to undo?".
Contents
The path checks the implementation, the rights, the practice model, the refusals, the data, the operating rule and the situations where the pilot must be abandoned.
Check the implementation and the version
MCP is a protocol; Archicad capabilities depend on the server, the bridge and the APIs used. Two projects with the same name can expose different actions. Read the code, the documentation and the compatibilities before installing.
The Graphisoft developer documentation presents the extension paths of Archicad. The MCP specification describes communication between client and server. Neither of these pages validates any particular third-party connector.
Record the version of Archicad, of the server, of the AI client and of the system. Note the dependencies and the network access. If an update breaks the integration, the team must know how to revert to the previous configuration or disable the component.
Map the rights before the model
A user who can request an action should not necessarily be able to validate it. Archicad rights, the AI client accounts and the server permissions must form a coherent chain.
| Action | Risk | Recommended gate |
|---|---|---|
| read properties | information exposure | practice model and log |
| propose a classification | wrong business rule | preview and BIM validation |
| modify an element | model inconsistency | limited selection and copy |
| act on a shared file | conflict and responsibility | outside the first pilot |
Avoid tokens or secrets shared in an unprotected configuration file. Assign an owner to the server and a business lead to the rules applied. Technical access does not amount to project authorisation.
Prepare a practice model
The training model must contain the difficulties the pilot needs to learn to handle, without containing client data. A model that is too clean produces a demonstration, not an acceptance test.
Add a few badly named elements, a missing property, a locked object and two close classifications. Keep a reference state. Learners must compare the server output with a schedule or a native check.
Hypothetical implementation. The server could read the properties of a selection, spot those that are missing and propose a list of corrections. The BIM user would choose the authorised elements before any write. This scenario describes a possible test; Educasium does not present it as a real deployment.
The Educasium resource Archicad MCP helps identify the technical subject. This guide stays focused on the decision and training method.
Acceptance-test the outputs and the refusals
A well-evaluated server must know how to refuse an out-of-scope action. Test the refusals as much as the successes: no selection, reserved element, unknown attribute, incompatible version and repeated command.
Each test records the input, the call, the output and the final state in Archicad. A "done" response is not proof. Check the properties, the elements created, the layer structure and the effects on schedules.
The guide Archicad or Revit covers the BIM choice. MCP should not be used to reopen that choice: the pilot must respect the software and the conventions already decided. Our comparison of AI software for architecture is a reminder that the agency flow takes precedence over an isolated feature.
Frame the data and the shared work
Shared work adds actors and states that the first pilot must avoid. A modification can conflict with the project reservations, roles or validations. Start outside the collaborative environment.
Also check what information goes to the client or the model: properties, names, previews, prompts and logs. The ANSSI provides a useful security framework. The Educasium article on AI confidentiality helps classify data before the trial.
Bounded experience
Educasium does not claim any MCP Archicad installation in production at a client. The proposed framework aims at training on a practice model, with read before write and human validation. No quantified gain is promised.
Our view is that a successful pilot produces a list of authorised and forbidden capabilities. That list is more useful than an open demonstration, because it lets the BIM lead decide what can join the real flow.
Turn the acceptance test into an operating rule
The pilot result must become a matrix: action, authorised role, environment, validation and recovery procedure. A command may be allowed on a practice model and remain forbidden on a shared file. This distinction prevents the implicit move from training to production.
Also plan a check after each update. Re-run the edge cases and compare the logs before re-enabling writing. If the team does not have time to maintain this acceptance test, it probably does not have the capacity to operate the server durably.
Limits and counter-cases
A dedicated Archicad extension or a native control may be more appropriate for a deterministic rule. MCP adds a conversational layer and a component to maintain. It should not be added merely because the technology is new.
Stop the test if the server is not auditable, if the rights are not separable or if the action cannot be previewed. Do not use a shared file as a learning ground. A practice model is less spectacular, but far more informative.
Frequently asked questions
Does MCP Archicad work with all versions?
It depends on the implementation, the bridge and the APIs it uses. Check the compatibility matrix and reproduce the test on the target version. Do not infer compatibility from a video. Also document the procedure after an update.
Can it modify a shared project?
An implementation may expose write actions, but shared work adds rights and conflicts. It is not a good first case. Test first on a synthetic local copy. Any extension to the shared project must be approved by the BIM and security leads.
How do you check a proposed classification?
Display the element, the previous value, the proposal and the rule applied. Have the rule validated by the competent person. Test ambiguous cases and missing properties. A plausible classification may still be incompatible with the project convention.
Who should maintain the server?
A clearly designated person or team, able to track versions and dependencies. The BIM lead must not discover an update at the moment of a failure. Plan for deactivation and rollback. Responsibility must be written down before the pilot.
Organise a workshop on a practice model
Training eligible for OPCO/FIF PL funding subject to conditions. Qualiopi-certified organisation. Discover the AI training for architects or contact Educasium to build a test compatible with your conventions.